From: Matthias Brugger <matthias.bgg@gmail.com>
To: AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
matthias.bgg@kernel.org, arm@kernel.org, soc@kernel.org,
arnd@arndb.de, olof@lixom.net
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: Update entry for MediaTek SoC support
Date: Thu, 2 Feb 2023 10:55:14 +0100 [thread overview]
Message-ID: <1423871e-7dd1-4582-3bb9-85913868e951@gmail.com> (raw)
In-Reply-To: <4db8fb55-a02b-d98e-65f4-1a095c43104f@collabora.com>
On 02/02/2023 10:08, AngeloGioacchino Del Regno wrote:
> Il 01/02/23 16:22, matthias.bgg@kernel.org ha scritto:
>> From: Matthias Brugger <matthias.bgg@gmail.com>
>>
>> The linux-mediatek IRC channel has moved to liber.chat for quite some
>> time. Apart from that, not all patches are also send to LKML, so add
>> this ML explicitly.
>>
>> And last but not least:
>> Angelo does a wunderfull job in reviewing patches for all kind of
>> devices from MediaTek.
>>
>> Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
>> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>
> Is a R-b tag appropriate here to say "yes, go on with setting me as a reviewer"?
>
> Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
In general yes, but I think it got already merged :D
>
> P.S.: Thank you :-)
>
Thank you to you for all the effort!
Regards,
Matthias
> Cheers,
> Angelo
>
prev parent reply other threads:[~2023-02-02 9:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 15:22 [PATCH] MAINTAINERS: Update entry for MediaTek SoC support matthias.bgg
2023-02-01 16:30 ` patchwork-bot+linux-soc
2023-02-02 9:08 ` AngeloGioacchino Del Regno
2023-02-02 9:55 ` Matthias Brugger [this message]
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=1423871e-7dd1-4582-3bb9-85913868e951@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.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