From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 5/8] Broadcom maintainers changes for 4.6
Date: Sat, 20 Feb 2016 11:46:24 -0800 [thread overview]
Message-ID: <1455997587-17564-5-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1455997587-17564-1-git-send-email-f.fainelli@gmail.com>
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.6/maintainers
for you to fetch changes up to 20de823e8b38119d8106aa85e0bd8b47eb295889:
MAINTAINERS: ARM: BCM63xx: Update git and mailing-lists (2016-02-02 10:47:47 -0800)
----------------------------------------------------------------
This pull request contains MAINTAINERS file updates for Broadcom ARM-based SoCs:
- Florian updates the Broadcom BCM63xx ARM-based DSL SoCs to use the same mailing-list
and development tree as all the other Broadcom SoCS
----------------------------------------------------------------
Florian Fainelli (1):
MAINTAINERS: ARM: BCM63xx: Update git and mailing-lists
MAINTAINERS | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
next prev parent reply other threads:[~2016-02-20 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 19:46 [GIT PULL 1/8] Broadcom soc changes for 4.6 Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 2/8] Broadcom soc-arm64 " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 3/8] Broadcom devicetree " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 4/8] Broadcom devicetree-arm64 " Florian Fainelli
2016-02-20 19:46 ` Florian Fainelli [this message]
2016-02-20 19:46 ` [GIT PULL 6/8] Broadcom maintainers-arm64 " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 7/8] Broadcom defconfig " Florian Fainelli
2016-02-20 19:46 ` [GIT PULL 8/8] Broadcom defconfig-arm64 " Florian Fainelli
2016-02-26 23:00 ` [GIT PULL 1/8] Broadcom soc " Arnd Bergmann
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=1455997587-17564-5-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).