From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] BCM2835/6 changes for 4.5 (I hope)
Date: Thu, 31 Dec 2015 17:21:07 +0100 [thread overview]
Message-ID: <2793907.Tpb2ePsxfs@wuerfel> (raw)
In-Reply-To: <568499D7.8030400@gmail.com>
On Wednesday 30 December 2015 18:58:31 Florian Fainelli wrote:
> Le 28/12/2015 21:01, Eric Anholt a ?crit :
> > Apparently this is really late in the process (sorry! I still haven't
> > figured out the timelines.), but I'm hoping we could merge these
> > changes for 4.5. This includes the Raspberry Pi 2 port, with just two
> > minor fixes from the last submission.
> >
> > The reason I've been pushing hard to get pi2 in is:
> >
> > 1) It's a lot of conflict resolution every version since it requires
> > splitting the 2835 DT file.
> >
> > 2) People are generally using pi2 these days, so it means people are
> > more likely to upstream 2835 driver code if we have an upstream port
> > they can run.
> >
> > Testing status: kbuild test robot builds passed. Boot tested each
> > branch head on pi1. Boot tested the merge of all 4 branches on pi1.
> > Boot tested the merge of all 4 branches on pi2, with and without the
> > irqchip fixes.
>
> Considering that we are fairly late for v4.5, I would prefer if Arnd,
> Olof or Kevin could take these directly into their respective branches,
> if this is really really too late, then I will queue these changes, and
> the next ones you have for v4.6.
>
> Thanks and happy holidays!
>
I've merged them now into the respective branches. However, I only
merged the usb-fixes branch for the first two (next/soc and next/drivers)
and decided to cherry-pick the patches from the other two branches
into next/dt and next/defconfig, to minimize the amount of backmerges
when the changes in those branches are clearly not meant to be useful
by themselves without at least the first branch merged in as well.
Please follow up with one more patch to enable bcm2836 in multi_v7_defconfig.
Arnd
prev parent reply other threads:[~2015-12-31 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 5:01 [GIT PULL] BCM2835/6 changes for 4.5 (I hope) Eric Anholt
2015-12-29 5:01 ` [GIT PULL 1/4] BCM2835 SOC changes for 4.5 Eric Anholt
2015-12-29 5:01 ` [GIT PULL 2/4] BCM2835 drivers " Eric Anholt
2016-01-07 14:48 ` Arnd Bergmann
2015-12-29 5:01 ` [GIT PULL 3/4] BCM2835 DT " Eric Anholt
2015-12-29 5:01 ` [GIT PULL 4/4] BCM2835 defconfig " Eric Anholt
2015-12-31 2:58 ` [GIT PULL] BCM2835/6 changes for 4.5 (I hope) Florian Fainelli
2015-12-31 16:21 ` Arnd Bergmann [this message]
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=2793907.Tpb2ePsxfs@wuerfel \
--to=arnd@arndb.de \
--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).