From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 3/3] Broadcom maintainers-arm64 fixes for 4.18
Date: Tue, 19 Jun 2018 16:31:04 -0700 [thread overview]
Message-ID: <20180619233104.32173-3-f.fainelli@gmail.com> (raw)
In-Reply-To: <20180619233104.32173-1-f.fainelli@gmail.com>
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.18/maintainers-arm64-fixes
for you to fetch changes up to d64324acdb7052b08b13ffc8c12af232c6a29afd:
MAINTAINERS: Update Broadcom iProc entry with Stingray (2018-06-18 09:28:36 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs MAINTAINERS file
fixes for 4.18, please pull the following:
- Florian fixes the entry for the Northstar2 SoCs which was somehow lost
during a directory move. He also adds an entry for the Stingray SoCs
which was missing from the day files were added
----------------------------------------------------------------
Florian Fainelli (2):
MAINAINTERS: Corrected Broadcom Northstar2 entry
MAINTAINERS: Update Broadcom iProc entry with Stingray
MAINTAINERS | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
next prev parent reply other threads:[~2018-06-19 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 23:31 [GIT PULL 1/3] Broadcom devicetree fixes for 4.18 Florian Fainelli
2018-06-19 23:31 ` [GIT PULL 2/3] Broadcom devicetree-arm64 " Florian Fainelli
2018-06-23 17:21 ` Olof Johansson
2018-06-23 18:49 ` Florian Fainelli
2018-06-19 23:31 ` Florian Fainelli [this message]
2018-06-23 17:22 ` [GIT PULL 3/3] Broadcom maintainers-arm64 " Olof Johansson
2018-06-23 17:20 ` [GIT PULL 1/3] Broadcom devicetree " Olof Johansson
2018-06-23 18:48 ` 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=20180619233104.32173-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