From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/5] Broadcom maintainers changes for 4.15
Date: Fri, 20 Oct 2017 17:16:34 -0700 [thread overview]
Message-ID: <20171021001636.17662-3-f.fainelli@gmail.com> (raw)
In-Reply-To: <20171021001636.17662-1-f.fainelli@gmail.com>
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.15/maintainers
for you to fetch changes up to 97b79f90f199cce820a6d4aeff3ba0125114bbf7:
MAINTAINERS: Update Broadcom iProc regexp with Hurricane 2 (2017-10-12 11:29:42 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM-based SoCs MAINTAINERS file update for
4.15, please pull the following:
- Florian updates the MAINTAINERS entry for Broadcom SoCs with the Hurricane 2 regexp
to match new files being added
----------------------------------------------------------------
Florian Fainelli (1):
MAINTAINERS: Update Broadcom iProc regexp with Hurricane 2
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
next prev parent reply other threads:[~2017-10-21 0:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-21 0:16 [GIT PULL 1/5] Broadcom soc changes for 4.15 (part 2) Florian Fainelli
2017-10-21 0:16 ` [GIT PULL 2/5] Broadcom devicetree changes for 4.15 Florian Fainelli
2017-10-30 12:13 ` Arnd Bergmann
2017-10-21 0:16 ` Florian Fainelli [this message]
2017-10-30 10:18 ` [GIT PULL 3/5] Broadcom maintainers " Arnd Bergmann
2017-10-21 0:16 ` [GIT PULL 4/5] Broadcom defconfig " Florian Fainelli
2017-10-30 10:02 ` Arnd Bergmann
2017-10-21 0:16 ` [GIT PULL 5/5] Broadcom drivers changes for 4.15 (part 2) Florian Fainelli
2017-11-02 15:22 ` Arnd Bergmann
2017-10-30 10:08 ` [GIT PULL 1/5] 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=20171021001636.17662-3-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).