From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Eric Anholt <eric@anholt.net>
Subject: [GIT PULL 1/2] bcm2835 changes to defconfigs for 4.6
Date: Wed, 17 Feb 2016 18:56:47 -0800 [thread overview]
Message-ID: <1455764208-5679-1-git-send-email-eric@anholt.net> (raw)
The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d:
Linux 4.5-rc1 (2016-01-24 13:06:47 -0800)
are available in the git repository at:
git@github.com:anholt/linux.git bcm2835-defconfig-next-2016-02-17
for you to fetch changes up to 0a05d3b71ada526ef93019fb3fbd6a95561a8a5f:
ARM: multi_v7_defconfig: Enable BCM283x (2016-02-17 11:18:05 -0800)
----------------------------------------------------------------
This pull request brings in defconfig changes to enable bcm2836 in the
2835 and multi_v7 defconfigs.
----------------------------------------------------------------
Daniel Stone (1):
ARM: multi_v7_defconfig: Enable BCM283x
Stefan Wahren (2):
ARM: bcm2835_defconfig: Enable RPi firmware driver
ARM: bcm2835_defconfig: Enable RPi power domain driver
Stephen Warren (3):
ARM: bcm2835_defconfig: rebuild on next-20160205
ARM: bcm2835_defconfig: disable DEBUG_LL
ARM: bcm2835_defconfig: enable ARMv7 support
arch/arm/configs/bcm2835_defconfig | 11 +++++------
arch/arm/configs/multi_v7_defconfig | 12 ++++++++++++
2 files changed, 17 insertions(+), 6 deletions(-)
next reply other threads:[~2016-02-18 2:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 2:56 Eric Anholt [this message]
2016-02-18 2:56 ` [GIT PULL 2/2] bcm2835 changes to DT " Eric Anholt
2016-02-18 20:12 ` Florian Fainelli
2016-02-20 19:07 ` Florian Fainelli
2016-02-18 20:13 ` [GIT PULL 1/2] bcm2835 changes to defconfigs " Florian Fainelli
2016-02-19 22:37 ` Florian Fainelli
2016-02-20 19:31 ` 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=1455764208-5679-1-git-send-email-eric@anholt.net \
--to=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®