public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Cc: nfraprado@collabora.com, wenst@chromium.org, robh@kernel.org,
	amergnat@baylibre.com, arnd@arndb.de
Subject: Re: [PATCH] MAINTAINERS: Add Angelo as MediaTek SoC co-maintainer
Date: Mon, 2 Oct 2023 12:20:17 +0200	[thread overview]
Message-ID: <77bfcbca-e7fe-49e1-952a-c99596160c0f@collabora.com> (raw)
In-Reply-To: <d26ee3f8-d5d3-e46d-4d79-098992d13790@gmail.com>

Il 02/10/23 11:41, Matthias Brugger ha scritto:
> 
> 
> On 29/09/2023 10: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>
> 
> Thanks Angelo to volunteer on this. It actually was on my list for the last days to 
> ask you to help me out as I'm not able at the moment to cope with the review 
> process. That's unfortunate and we missed one merge window (August) where I took no 
> patches but after holiday situation didn't get better. I don't want to be break in 
> the MediaTek upstream development, so it's great to see you stepping up.
> 
> As I read in the thread, I agree the best will be to have a share tree at 
> kernel.org. It seems I can't share my tree with you, so hopefully you will get 
> access fast.
> 
> My idea is to not disappear and create a collaborative process for us on the 
> maintainership in the future.
> 

I am really happy first of all see that you're fine, and then to see that you
are happy with me going for this.

I will be even happier to create a collaborative process for our maintainership
of MediaTek, as I was really hoping for that to happen.

>> ---
>>
>> 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.
> 
> I think you didn't tried matthias.bgg@kernel.org, but that should be no excuse from 
> my side for being unresponsive. Thanks for your help!
> 
> Please contact me on IRC for any coordination.

Coming to IRC for a nice chat ASAP!
Thank *you* for this email, and preventively thanks for *your* help!

Cheers,
Angelo

> 
> Regards,
> Matthias
> 
> 
>>
>> 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/
>>
>>   MAINTAINERS | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 208cfcc1aee3..211a8322c801 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -2330,7 +2330,7 @@ F:    drivers/rtc/rtc-mt7622.c
>>   ARM/Mediatek SoC support
>>   M:    Matthias Brugger <matthias.bgg@gmail.com>
>> -R:    AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> +M:    AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>>   L:    linux-kernel@vger.kernel.org
>>   L:    linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>>   L:    linux-mediatek@lists.infradead.org (moderated for non-subscribers)


  reply	other threads:[~2023-10-02 10:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-29  8:20 [PATCH] MAINTAINERS: Add Angelo as MediaTek SoC co-maintainer AngeloGioacchino Del Regno
2023-09-29 19:36 ` Arnd Bergmann
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 [this message]
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=77bfcbca-e7fe-49e1-952a-c99596160c0f@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=amergnat@baylibre.com \
    --cc=arnd@arndb.de \
    --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=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