[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f653b23f-cf25-61ec-60d4-91dd7823edd2@microchip.com>
Date: Fri, 6 Jan 2023 16:59:52 +0100
From: Nicolas Ferre <nicolas.ferre@...rochip.com>
To: Miquel Raynal <miquel.raynal@...tlin.com>,
Tudor Ambarus <tudor.ambarus@...aro.org>
CC: <arnd@...db.de>, <richard@....at>,
<krzysztof.kozlowski+dt@...aro.org>, <herbert@...dor.apana.org.au>,
<robh+dt@...nel.org>, <akpm@...ux-foundation.org>,
<claudiu.beznea@...rochip.com>, <broonie@...nel.org>,
<linux-kernel@...r.kernel.org>, <linux-crypto@...r.kernel.org>,
<devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-spi@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
<pratyush@...nel.org>, <michael@...le.cc>,
Tudor Ambarus <tudor.ambarus@...rochip.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v2] MAINTAINERS: Update email of Tudor Ambarus
On 06/01/2023 at 16:55, Miquel Raynal wrote:
> Hey Tudor, hello all,
>
> tudor.ambarus@...aro.org wrote on Fri, 6 Jan 2023 17:45:20 +0200:
>
>> Miquel,
>>
>> Since we don't have an answer from Arnd, would you please queue this to
>> mtd/fixes?
>
> Are MAINTAINERS changes accepted through fixes PR? I see a number of
> experienced people in Cc:, I would like to hear from you folks, because
> I never had to do that before. If yes, then I'll do it right away,
> otherwise I'll apply to mtd/next. I'm all ears :)
I remember a conversation that stated that MAINTAINERS changes must land
in Linus' tree the quickest, because it'll just avoid confusion and
bouncing emails.
My $0.2...
Regards,
Nicolas
--
Nicolas Ferre
Powered by blists - more mailing lists