From: Florian Fainelli <florian.fainelli@broadcom.com>
To: soc@kernel.org
Cc: Andrea della Porta <andrea.porta@suse.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
khilman@kernel.org, bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 5/5] Broadcom maintainers changes for 6.17
Date: Mon, 30 Jun 2025 12:02:16 -0700 [thread overview]
Message-ID: <20250630190216.1518354-5-florian.fainelli@broadcom.com> (raw)
In-Reply-To: <20250630190216.1518354-1-florian.fainelli@broadcom.com>
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.17/maintainers
for you to fetch changes up to 4a525d5d3150a3e387cb841f927f07eb4a98c368:
MAINTAINERS: add Raspberry Pi RP1 section (2025-06-09 10:11:39 -0700)
----------------------------------------------------------------
This pull request contains MAINTAINERS file updates for 6.17, please
pull the following:
- Andrea adds the RP1 entry for all of the drivers pertaining to that
chip
----------------------------------------------------------------
Andrea della Porta (1):
MAINTAINERS: add Raspberry Pi RP1 section
MAINTAINERS | 8 ++++++++
1 file changed, 8 insertions(+)
prev parent reply other threads:[~2025-06-30 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 19:02 [GIT PULL 1/5] Broadcom defconfig-arm64 changes for 6.17 Florian Fainelli
2025-06-30 19:02 ` [GIT PULL 2/5] Broadcom devicetree " Florian Fainelli
2025-06-30 19:02 ` [GIT PULL 3/5] Broadcom devicetree-arm64 " Florian Fainelli
2025-06-30 19:02 ` [GIT PULL 4/5] Broadcom drivers " Florian Fainelli
2025-07-01 5:11 ` Greg Kroah-Hartman
2025-07-01 10:11 ` Andrea della Porta
2025-06-30 19:02 ` Florian Fainelli [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=20250630190216.1518354-5-florian.fainelli@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=andrea.porta@suse.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--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