From: "Arnd Bergmann" <arnd@arndb.de>
To: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Cc: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
wenst@chromium.org, "Matthias Brugger" <matthias.bgg@gmail.com>,
"Rob Herring" <robh@kernel.org>,
amergnat@baylibre.com, "Stephen Rothwell" <sfr@canb.auug.org.au>
Subject: Re: [PATCH] MAINTAINERS: Add Angelo as MediaTek SoC co-maintainer
Date: Fri, 29 Sep 2023 15:36:57 -0400 [thread overview]
Message-ID: <84b2de54-8337-42a3-a25c-a95cf2f3349f@app.fastmail.com> (raw)
In-Reply-To: <20230929082009.71843-1-angelogioacchino.delregno@collabora.com>
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
- 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.
Arnd
next prev parent reply other threads:[~2023-09-29 19:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 8:20 AngeloGioacchino Del Regno
2023-09-29 19:36 ` Arnd Bergmann [this message]
2023-10-02 3:30 ` Chen-Yu Tsai
2023-10-02 8:27 ` AngeloGioacchino Del Regno
2023-10-02 9:04 ` Chen-Yu Tsai
2023-09-30 7:55 ` Frank Wunderlich
2023-10-02 3:31 ` Chen-Yu Tsai
2023-10-02 9:41 ` Matthias Brugger
2023-10-02 10:20 ` AngeloGioacchino Del Regno
2023-10-04 12:18 ` Alexandre Mergnat
2023-10-02 10:23 ` Matthias Brugger
2023-10-04 18:08 ` Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84b2de54-8337-42a3-a25c-a95cf2f3349f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=wenst@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®