From: "Arnd Bergmann" <arnd@arndb.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Florian Fainelli" <florian.fainelli@broadcom.com>
Cc: "Pengutronix Kernel Team" <kernel@pengutronix.de>,
soc@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Fix Florian Fainelli's email address
Date: Fri, 29 Sep 2023 15:13:35 -0400 [thread overview]
Message-ID: <b0fdfb95-dcd9-4d63-9e72-5a985808de3f@app.fastmail.com> (raw)
In-Reply-To: <20230929060114.zbex7z4atuzojs45@pengutronix.de>
On Fri, Sep 29, 2023, at 02:01, Uwe Kleine-König wrote:
> On Thu, Sep 28, 2023 at 11:21:50PM +0200, Florian Fainelli wrote:
>> On 9/28/2023 9:06 AM, Uwe Kleine-König wrote:
>> > Commit 31345a0f5901 ("MAINTAINERS: Replace my email address") added 13
>> > instances of ...@broadcom.com and one of only ...@broadcom. I didn't
>> > double check if Broadcom really owns that TLD, but git send-email
>> > doesn't accept it, so add ".com" to that one bogous(?) instance.
>> >
>> > Fixes: 31345a0f5901 ("MAINTAINERS: Replace my email address")
>> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
>>
>> Embarrassing, thanks for fixing this Uwe!
>>
>> Acked-by: Florian Fainelli <florian.fainelli@broadcom.com>
>
> Who picks this up? 31345a0f5901 went in via arm-soc. Arnd, will you?
>
Yes, I've already included it in the arm/fixes branch now, doing
some final testing on the branch before I send the PR.
Arnd
prev parent reply other threads:[~2023-09-29 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 7:06 Uwe Kleine-König
2023-09-28 21:21 ` Florian Fainelli
2023-09-29 6:01 ` Uwe Kleine-König
2023-09-29 19:13 ` Arnd Bergmann [this message]
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=b0fdfb95-dcd9-4d63-9e72-5a985808de3f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=florian.fainelli@broadcom.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.org \
--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
all inboxes | Powered by JetHome®