From: Jakub Kicinski <kuba@kernel.org>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>
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: Mon, 7 Aug 2023 12:25:08 -0700 [thread overview]
Message-ID: <20230807122508.403c1972@kernel.org> (raw)
In-Reply-To: <20230804050007.235799-1-claudiu.beznea@tuxon.dev>
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? If nobody speaks up we can pick it up in networking
and send to Linus on Thu.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Claudiu Beznea <claudiu.beznea@tuxon.dev>
Cc: linux-pwm@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, edumazet@google.com,
linux-pm@vger.kernel.org, maz@kernel.org, tiwai@suse.com,
lgirdwood@gmail.com, conor.dooley@microchip.com,
broonie@kernel.org, srinivas.kandagatla@linaro.org,
sre@kernel.org, u.kleine-koenig@pengutronix.de, perex@perex.cz,
thierry.reding@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, davem@davemloft.net,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] MAINTAINERS: update Claudiu Beznea's email address
Date: Mon, 7 Aug 2023 12:25:08 -0700 [thread overview]
Message-ID: <20230807122508.403c1972@kernel.org> (raw)
In-Reply-To: <20230804050007.235799-1-claudiu.beznea@tuxon.dev>
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? If nobody speaks up we can pick it up in networking
and send to Linus on Thu.
_______________________________________________
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-08-07 19:26 UTC|newest]
Thread overview: 22+ 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 5:00 ` Claudiu Beznea
2023-08-04 12:23 ` Sebastian Reichel
2023-08-04 12:23 ` Sebastian Reichel
2023-08-04 13:47 ` Jiri Pirko
2023-08-04 13:47 ` Jiri Pirko
2023-08-10 9:59 ` Simon Horman
2023-08-10 9:59 ` Simon Horman
2023-08-10 10:30 ` claudiu beznea
2023-08-10 10:30 ` claudiu beznea
2023-08-07 19:25 ` Jakub Kicinski [this message]
2023-08-07 19:25 ` Jakub Kicinski
2023-08-08 5:21 ` claudiu beznea
2023-08-08 5:21 ` claudiu beznea
2023-08-08 22:00 ` patchwork-bot+netdevbpf
2023-08-08 22:00 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 18:38 Claudiu Beznea
2023-07-14 19:04 ` Conor Dooley
2023-07-17 13:26 ` Nicolas Ferre
2023-07-17 13:26 ` Nicolas Ferre
2023-07-28 15:36 ` Conor Dooley
2023-07-31 4:59 ` claudiu beznea
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=20230807122508.403c1972@kernel.org \
--to=kuba@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.