From: Rob Herring <robh@kernel.org>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: alexandre.belloni@bootlin.com, linux-mtd@lists.infradead.org,
krzysztof.kozlowski+dt@linaro.org, miquel.raynal@bootlin.com,
herbert@gondor.apana.org.au, anup@brainfault.org,
colin.i.king@gmail.com, devicetree@vger.kernel.org,
arnd@arndb.de, quic_abhinavk@quicinc.com, broonie@kernel.org,
baolin.wang@linux.alibaba.com, atishp@atishpatra.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, qyousef@layalina.io,
linux-spi@vger.kernel.org, michael@walle.cc, robh+dt@kernel.org,
linux-crypto@vger.kernel.org, richard@nod.at,
akpm@linux-foundation.org, vasily.averin@linux.dev,
claudiu.beznea@microchip.com, pratyush@kernel.org, tkhai@ya.ru
Subject: Re: [PATCH] MAINTAINERS: Update email of Tudor Ambarus
Date: Sun, 27 Nov 2022 12:25:52 -0600 [thread overview]
Message-ID: <166957354583.148471.5381866020763010078.robh@kernel.org> (raw)
In-Reply-To: <20221122125244.175295-1-tudor.ambarus@microchip.com>
On Tue, 22 Nov 2022 14:52:44 +0200, Tudor Ambarus wrote:
> My professional email will change and the microchip one will bounce after
> mid-november of 2022.
>
> Update the MAINTAINERS file, the YAML bindings, MODULE_AUTHOR entries and
> author mentions, and add an entry in the .mailmap file.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
> ---
> .mailmap | 1 +
> .../bindings/crypto/atmel,at91sam9g46-aes.yaml | 2 +-
> .../bindings/crypto/atmel,at91sam9g46-sha.yaml | 2 +-
> .../bindings/crypto/atmel,at91sam9g46-tdes.yaml | 2 +-
> .../devicetree/bindings/spi/atmel,at91rm9200-spi.yaml | 2 +-
> .../devicetree/bindings/spi/atmel,quadspi.yaml | 2 +-
> MAINTAINERS | 10 +++++-----
> drivers/crypto/atmel-ecc.c | 4 ++--
> drivers/crypto/atmel-i2c.c | 4 ++--
> drivers/crypto/atmel-i2c.h | 2 +-
> 10 files changed, 16 insertions(+), 15 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
_______________________________________________
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:[~2022-11-27 18:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:52 [PATCH] MAINTAINERS: Update email of Tudor Ambarus Tudor Ambarus
2022-11-22 13:13 ` Nicolas Ferre
2022-11-22 13:15 ` Arnd Bergmann
2022-11-24 11:02 ` Krzysztof Kozlowski
2022-11-22 13:23 ` Mark Brown
2022-11-25 4:45 ` Herbert Xu
2022-11-27 18:25 ` Rob Herring [this message]
2022-11-27 22:42 ` Pratyush Yadav
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=166957354583.148471.5381866020763010078.robh@kernel.org \
--to=robh@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=anup@brainfault.org \
--cc=arnd@arndb.de \
--cc=atishp@atishpatra.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@microchip.com \
--cc=colin.i.king@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=krzysztof.kozlowski+dt@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=pratyush@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=qyousef@layalina.io \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=tkhai@ya.ru \
--cc=tudor.ambarus@microchip.com \
--cc=vasily.averin@linux.dev \
/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