From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: soc for v4.9 (#1)
Date: Tue, 20 Sep 2016 11:45:50 +0200 [thread overview]
Message-ID: <5238448.m4YaC7vVme@wuerfel> (raw)
In-Reply-To: <87shsv6ni8.fsf@free-electrons.com>
On Tuesday, September 20, 2016 9:25:51 AM CEST Gregory CLEMENT wrote:
> Hi Arnd,
>
> On lun., sept. 19 2016, Arnd Bergmann <arnd@arndb.de> wrote:
>
> > On Monday, September 19, 2016 11:46:22 PM CEST Arnd Bergmann wrote:
> >> On Wednesday, September 14, 2016 5:34:37 PM CEST Gregory CLEMENT wrote:
> >> > mvebu soc for 4.9 (part 1)
> >> >
> >> > - irq cleanup for old mvebu SoC
> >> > - Convert orion5x based SoC Netgear WNR854T to devicetree
> >> >
> >>
> >> Pulled into next/soc, thanks!
> >
> > Sorry, backed out again after seeing the PCI stuff on the WNR854T in
> > there. I thought the plan was to leave out PCI support from the DT
> > based machine file, and leave the old board in place, or am I
> > missing something?
>
> I might have overlooked the thread, I thouhgt the state of the patch was
> OK as is, and further changes can be done later.
>
> So it seems that it will be 4.10 material.
>
We have gained a little more time since Linus delayed the merge window
by another week, so I think there is still a chance to respin this.
I also really want the NO_IRQ changes to get merged ;-)
Just drop the patch removing wnr854t-setup.c, and add another patch
on top to remove the PCI initialization from wrt350n-v2-setup.c,
and I'll take it.
Arnd
next prev parent reply other threads:[~2016-09-20 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 15:34 [GIT PULL] ARM: mvebu: soc for v4.9 (#1) Gregory CLEMENT
2016-09-19 21:46 ` Arnd Bergmann
2016-09-19 21:49 ` Arnd Bergmann
2016-09-20 7:25 ` Gregory CLEMENT
2016-09-20 9:45 ` Arnd Bergmann [this message]
2016-09-20 16:43 ` Gregory CLEMENT
2016-09-21 8:10 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2016-09-21 10:19 Gregory CLEMENT
2016-09-21 20:36 ` 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=5238448.m4YaC7vVme@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