From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Nicolas Saenz Julienne <nsaenz@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
olof@lixom.net, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 2/2] Broadcom maintainers fixes for 5.19
Date: Wed, 8 Jun 2022 02:31:32 -0700 [thread overview]
Message-ID: <20220608093132.1465703-2-f.fainelli@gmail.com> (raw)
In-Reply-To: <20220608093132.1465703-1-f.fainelli@gmail.com>
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.19/maintainers-fixes
for you to fetch changes up to 46d6e11320d21dc40fce229ab3504125847de27e:
MAINTAINERS: Update BCM2711/BCM2835 maintainer (2022-06-08 01:00:47 -0700)
----------------------------------------------------------------
This pull request contains MAINTAINERS file update for Broadcom SoCs,
please pull the following:
- Nicolas steps down from maintaining the BCM283x/BCM2711 (Raspberry
Pi) architecture and designates Florian to take care of that
----------------------------------------------------------------
Nicolas Saenz Julienne (1):
MAINTAINERS: Update BCM2711/BCM2835 maintainer
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
_______________________________________________
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-06-08 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 9:31 [GIT PULL 1/2] Broadcom drivers fixes for 5.19 Florian Fainelli
2022-06-08 9:31 ` Florian Fainelli [this message]
2022-06-08 12:43 ` [GIT PULL 2/2] Broadcom maintainers " Florian Fainelli
2022-06-13 17:20 ` Florian Fainelli
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=20220608093132.1465703-2-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nsaenz@kernel.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;
as well as URLs for NNTP newsgroup(s).