From: claudiu beznea <claudiu.beznea@tuxon.dev>
To: Jakub Kicinski <kuba@kernel.org>
Cc: nicolas.ferre@microchip.com, conor.dooley@microchip.com,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, maz@kernel.org, srinivas.kandagatla@linaro.org,
thierry.reding@gmail.com, u.kleine-koenig@pengutronix.de,
sre@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org, linux-pwm@vger.kernel.org,
alsa-devel@alsa-project.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update Claudiu Beznea's email address
Date: Tue, 8 Aug 2023 08:21:00 +0300 [thread overview]
Message-ID: <745d818d-fbfe-da02-b98d-bd7b2c5059ed@tuxon.dev> (raw)
In-Reply-To: <20230807122508.403c1972@kernel.org>
On 07.08.2023 22:25, Jakub Kicinski wrote:
> On Fri, 4 Aug 2023 08:00:07 +0300 Claudiu Beznea wrote:
>> Update MAINTAINERS entries with a valid email address as the Microchip
>> one is no longer valid.
>>
>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
>> Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
>> Signed-off-by: Claudiu Beznea <claudiu.beznea@tuxon.dev>
>
> Thanks for updating the email!
>
> A bit of a cross-tree change. Is there anyone in particular that you'd
> expect to apply it?
No.
> If nobody speaks up we can pick it up in networking
> and send to Linus on Thu.
That would be good.
Thank you,
Claudiu Beznea
next prev parent reply other threads:[~2023-08-08 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 5:00 [PATCH] MAINTAINERS: update Claudiu Beznea's email address Claudiu Beznea
2023-08-04 12:23 ` Sebastian Reichel
2023-08-04 13:47 ` Jiri Pirko
2023-08-10 9:59 ` Simon Horman
2023-08-10 10:30 ` claudiu beznea
2023-08-07 19:25 ` Jakub Kicinski
2023-08-08 5:21 ` claudiu beznea [this message]
2023-08-08 22:00 ` patchwork-bot+netdevbpf
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=745d818d-fbfe-da02-b98d-bd7b2c5059ed@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maz@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=perex@perex.cz \
--cc=sre@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).