From: Andrew Morton <akpm@linux-foundation.org>
To: Nicolas Ferre <nicolas.ferre@microchip.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>, <arnd@arndb.de>,
<richard@nod.at>, <krzysztof.kozlowski+dt@linaro.org>,
<herbert@gondor.apana.org.au>, <robh+dt@kernel.org>,
<claudiu.beznea@microchip.com>, <broonie@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-spi@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
<pratyush@kernel.org>, <michael@walle.cc>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v2] MAINTAINERS: Update email of Tudor Ambarus
Date: Fri, 6 Jan 2023 16:47:51 -0800 [thread overview]
Message-ID: <20230106164751.7ddaf5c54e0a764344806848@linux-foundation.org> (raw)
In-Reply-To: <f653b23f-cf25-61ec-60d4-91dd7823edd2@microchip.com>
On Fri, 6 Jan 2023 16:59:52 +0100 Nicolas Ferre <nicolas.ferre@microchip.com> wrote:
> > 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.
Yes, I always merge MAINTAINERS fixes asap.
Probably these fixes should be backported into -stable kernels also -
we don't want incorrect email addresses in *any* kernel. But I don't
do that.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-07 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 14:40 [PATCH v2] MAINTAINERS: Update email of Tudor Ambarus Tudor Ambarus
2022-12-26 14:49 ` Tudor Ambarus
2023-01-06 15:45 ` Tudor Ambarus
2023-01-06 15:55 ` Miquel Raynal
2023-01-06 15:59 ` Nicolas Ferre
2023-01-07 0:47 ` Andrew Morton [this message]
2023-01-07 14:17 ` Miquel Raynal
2023-01-07 15:38 ` Miquel Raynal
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=20230106164751.7ddaf5c54e0a764344806848@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=tudor.ambarus@linaro.org \
--cc=tudor.ambarus@microchip.com \
/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