From: <Nicolas.Ferre@microchip.com>
To: <tudor.ambarus@linaro.org>, <Ryan.Wanner@microchip.com>,
<broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add myself as a maintainer for Microchip SPI
Date: Mon, 10 Jul 2023 08:35:59 +0000 [thread overview]
Message-ID: <646c6dad-0c47-f7ea-1493-8d546b80f016@microchip.com> (raw)
In-Reply-To: <9609c217-45b7-211b-7ec0-5e4275b1ed78@linaro.org>
On 10/07/2023 at 09:42, Tudor Ambarus wrote:
> Hi, Ryan,
>
> You should probably add in To/Cc linux-spi@vger.kernel.org
> if you want Mark to queue it.
>
> On 6/30/23 17:17, Ryan.Wanner@microchip.com wrote:
>> From: Ryan Wanner <Ryan.Wanner@microchip.com>
>>
>> Tudor is not with Microchip anymore. I have worked lately
>> with Microchip SPI drivers replacing Tudor with myself as this
>> maintainer.
>>
>
> Describe your changes in imperative mood.
>
> I agree to be replaced:
> Acked-by: Tudor Ambarus <tudor.ambarus@linaro.org>
Thanks Tudor. Good luck Ryan:
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Mark, please tell us if you want a v2 patch to be re-sent.
Best regards,
Nicolas
>> Signed-off-by: Ryan Wanner <Ryan.Wanner@microchip.com>
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index ad32db6c81cc..8478cc82f197 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -13881,7 +13881,7 @@ T: git https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/
>> F: drivers/soc/microchip/
>>
>> MICROCHIP SPI DRIVER
>> -M: Tudor Ambarus <tudor.ambarus@linaro.org>
>> +M: Ryan Wanner <ryan.wanner@microchip.com>
>> S: Supported
>> F: drivers/spi/spi-atmel.*
>>
>
--
Nicolas Ferre
next prev parent reply other threads:[~2023-07-10 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 16:17 Ryan.Wanner
2023-07-10 7:42 ` Tudor Ambarus
2023-07-10 8:35 ` Nicolas.Ferre [this message]
2023-07-12 10:36 ` Mark Brown
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=646c6dad-0c47-f7ea-1493-8d546b80f016@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Ryan.Wanner@microchip.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tudor.ambarus@linaro.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®