Messages in this thread | | | From | Chen-Yu Tsai <> | Date | Mon, 2 Oct 2023 11:30:13 +0800 | Subject | Re: [PATCH] MAINTAINERS: Add Angelo as MediaTek SoC co-maintainer |
| |
On Sat, Sep 30, 2023 at 3:37 AM Arnd Bergmann <arnd@arndb.de> wrote: > > On Fri, Sep 29, 2023, at 04:20, AngeloGioacchino Del Regno wrote: > > I am a top reviewer mainly for MediaTek SoC related patches in most > > subsystems and I've also been upstreaming both improvements, fixes > > and new drivers and devicetrees when required. > > > > The MediaTek scene saw a generous increase in number of patches that > > are sent to the lists every week, increasing the amount of required > > efforts to maintain the MTK bits overall, and we will possibly see > > even more of that. > > > > For this reason, and also because of suggestions and encouragement > > coming from the community, I'm stepping up to be a co-maintainer of > > MediaTek SoCs support. > > > > Signed-off-by: AngeloGioacchino Del Regno > > <angelogioacchino.delregno@collabora.com> > > --- > > > > P.S.: I tried to reach to Matthias for almost two months, but I couldn't > > find any way to talk to him and he has been unresponsive on the mailing > > lists as well. > > > > P.P.S.: This also comes after Rob Herring's suggestion to have myself as > > a MediaTek SoC co-maintainer [1] and support from other people. > > > > [1]: https://lore.kernel.org/all/20230804225813.12493-1-robh@kernel.org/ > > Thanks for volunteering for this! > > I have no information on what Mattias is doing, but I see that he > has not merged any patches since June, and that he never sent a > pull request for your patches that are still in his for-next > branch. > > I hope he's going to be ok, but let's plan for you to take over > for the moment, at least until Matthias is again able to keep > maintaining the platform in the near future. > > Here is my suggestion for how to continue from here: > > - Please send your MAINTAINERS file update to soc@kernel.org > along with any urgent bugfixes you may have, so I can forward > them for 6.7. I'm wrapping up the current set of fixes at > the moment, so this would be for next week's rc > > - Create a git tree with the ususal branches (drivers, soc, dt, > fixes, for-next) and ask Stephen Rothwell (on Cc) to add > the combined for-next branch to linux-next for integration testing
I suggest creating a shared git tree from the start. That way when Mattias comes back and does agree to co-maintainership, or if anyone else joins in, you don't have to change the git tree URL in a lot of places.
> - Start each branch on 6.6-rc2 (usually we use rc1, but this time > rc2 is a better candidate because of the last-minute > drivers/pmdomain rename), and merge the corresponding branches > from git://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git > into those to avoids conflicts with his tree > > - Add any further patches you want in 6.7 on top > > - Send a first set of pull requests to soc@kernel.org for whatever > you have merged as soon as you are confident about them, > ideally by the end of next week. > > - Send additional pull requests for fixups or late features in > the weeks after that as you see fit. > > See Documentation/process/maintainer-soc.rst for more details > on the above. When Mattias comes back, you can work out a new > process together with him.
I can also answer any questions you might have about the process.
ChenYu
| |