From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
arnd@arndb.de, khilman@kernel.org, olof@lixom.net,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/2] Broadcom late drivers changes for 5.12
Date: Tue, 16 Feb 2021 17:16:54 -0800 [thread overview]
Message-ID: <20210217011654.2561426-2-f.fainelli@gmail.com> (raw)
In-Reply-To: <20210217011654.2561426-1-f.fainelli@gmail.com>
The following changes since commit 8b8f095b9076ca61107c0910c9273afd1dfa1f04:
soc: bcm: brcmstb: Remove soc_is_brcmstb() (2021-01-27 09:36:41 -0800)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.12/drivers-part2
for you to fetch changes up to b22ac48b0a4d74415beef10e49e434e8f228a2bf:
MAINTAINERS: rectify BROADCOM PMB (POWER MANAGEMENT BUS) DRIVER (2021-02-08 13:19:23 -0800)
----------------------------------------------------------------
This pull request contains Broadcom ARM/ARM64 SoC drivers changes for
5.12:
- Lukas fixes an incorrect entry of the Broadcom PMB driver which still
referenced the location of the files from a previous submission
----------------------------------------------------------------
Lukas Bulwahn (1):
MAINTAINERS: rectify BROADCOM PMB (POWER MANAGEMENT BUS) DRIVER
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
_______________________________________________
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:[~2021-02-17 1:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 1:16 [GIT PULL 1/2] Broadcom late devicetree changes for 5.12 Florian Fainelli
2021-02-17 1:16 ` Florian Fainelli [this message]
2021-03-08 22:03 ` 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=20210217011654.2561426-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=lukas.bulwahn@gmail.com \
--cc=olof@lixom.net \
--cc=rafal@milecki.pl \
--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).