From: "Arnd Bergmann" <arnd@arndb.de>
To: "Florian Fainelli" <florian.fainelli@broadcom.com>, soc@kernel.org
Cc: "Justin Chen" <justin.chen@broadcom.com>,
"Kamal Dasu" <kamal.dasu@broadcom.com>,
linux-arm-kernel@lists.infradead.org,
"Olof Johansson" <olof@lixom.net>,
"Kevin Hilman" <khilman@kernel.org>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 3/3] Broadcom maintainers changes for 6.5
Date: Thu, 22 Jun 2023 17:29:34 +0200 [thread overview]
Message-ID: <cd9b66ab-e2c9-4255-b5a9-10ac83035969@app.fastmail.com> (raw)
In-Reply-To: <20230619134920.3384844-3-florian.fainelli@broadcom.com>
On Mon, Jun 19, 2023, at 15:49, Florian Fainelli wrote:
> The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
>
> Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.5/maintainers
>
> for you to fetch changes up to 825edae7d1c39171634253203f03cf6c6cf380bc:
>
> MAINTAINERS: Replace my email address (2023-06-19 04:48:28 -0700)
>
> ----------------------------------------------------------------
> This pull request contains MAINTAINERS file updates for 6.5, please pull
> the following:
>
> - Justin, Kamal and Florian update their email to use their corporate
> Broadcom email address
There was a small merge conflict against 80e62bc8487b0 ("MAINTAINERS:
re-sort all entries and fields"), should be all resolved now.
Arnd
next prev parent reply other threads:[~2023-06-22 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 13:49 [GIT PULL 1/3] Broadcom devicetree changes for 6.5 Florian Fainelli
2023-06-19 13:49 ` [GIT PULL 2/3] Broadcom devicetree-arm64 " Florian Fainelli
2023-06-19 13:49 ` [GIT PULL 3/3] Broadcom maintainers " Florian Fainelli
2023-06-22 15:29 ` Arnd Bergmann [this message]
2023-06-20 21:21 ` [GIT PULL 1/3] Broadcom devicetree " patchwork-bot+linux-soc
2023-06-22 16:10 ` patchwork-bot+linux-soc
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=cd9b66ab-e2c9-4255-b5a9-10ac83035969@app.fastmail.com \
--to=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=justin.chen@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
/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