From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/4] Broadcom defconfig-arm64 changes for 4.9 (part 2)
Date: Fri, 30 Sep 2016 12:23:15 -0700 [thread overview]
Message-ID: <1475263395-27653-4-git-send-email-f.fainelli@gmail.com> (raw)
In-Reply-To: <1475263395-27653-1-git-send-email-f.fainelli@gmail.com>
The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc:
Linux 4.8-rc1 (2016-08-07 18:18:00 -0700)
are available in the git repository at:
http://github.com/Broadcom/stblinux.git tags/arm-soc/for-4.9/defconfig-arm64
for you to fetch changes up to 51e3fb1d3f514cd336faf185df73b25fca194773:
Merge tag 'bcm2835-defconfig-64-next-2016-09-22' into defconfig-arm64/next (2016-09-30 12:02:29 -0700)
----------------------------------------------------------------
This pull request contains Broadcom ARM64-based SoCs defconfig changes for 4.9,
please pull the following changes:
- Eric updates the ARMv8 defconfig to contain everything that is needed to run
a 64-bit kernel on the Raspberry Pi 3
----------------------------------------------------------------
Eric Anholt (1):
arm64: Add BCM2835 (Raspberry Pi 3) support to the defconfig
Florian Fainelli (1):
Merge tag 'bcm2835-defconfig-64-next-2016-09-22' into defconfig-arm64/next
arch/arm64/configs/defconfig | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
next prev parent reply other threads:[~2016-09-30 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 19:23 [GIT PULL 1/4] Broadcom devicetree changes for 4.9 (part 2) Florian Fainelli
2016-09-30 19:23 ` [GIT PULL 2/4] Broadcom devicetree-arm64 " Florian Fainelli
2016-09-30 19:23 ` [GIT PULL 3/4] Broadcom defconfig " Florian Fainelli
2016-09-30 19:23 ` Florian Fainelli [this message]
2016-10-23 21:55 ` [GIT PULL 4/4] Broadcom defconfig-arm64 " Florian Fainelli
2016-10-23 23:50 ` Olof Johansson
2016-10-24 16:52 ` Florian Fainelli
2016-10-03 5:28 ` [GIT PULL 1/4] Broadcom devicetree " Olof Johansson
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=1475263395-27653-4-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).