From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] LPC32xx DTS changes for v4.4
Date: Sun, 06 Dec 2015 20:50:56 +0100 [thread overview]
Message-ID: <3112069.RxjfiMKgHG@wuerfel> (raw)
In-Reply-To: <56641DCB.5080600@mleia.com>
On Sunday 06 December 2015 13:36:43 Vladimir Zapolskiy wrote:
> On 29.11.2015 15:48, Vladimir Zapolskiy wrote:
> > Hi Arnd,
> >
> > On 18.11.2015 18:21, Vladimir Zapolskiy wrote:
> >> Hi arm-soc team,
> >>
> >> Please consider pulling these DTS changes for the NXP LPC32xx
> >> platform and related boards.
> >>
> >> The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
> >>
> >> Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
> >>
> >> are available in the git repository at:
> >>
> >> https://github.com/vzapolskiy/linux.git lpc32xx-dts
> >>
> >> for you to fetch changes up to aa29efb445f11506daca0db934331f144b38ddc4:
> >>
> >> arm: dts: lpc32xx: move USB controller subdevices into own device node (2015-11-18 18:01:27 +0200)
> >
> > this is an old reviewed series, I suppose it is too late to include it
> > into v4.4, should I resend the same pull request for v4.5?
> >
> > Or is it possible to merge it as is?
>
> Is there anything, what prevents this changes from being merged?
I have them on my radar, this has been another time where we are slow
to start merging things. I have merged a couple of other branches, but
none of the DT changes for any platform so far.
I've just verified that the branch still merges fine into the current
kernel, otherwise I'd ask you to resubmit it based on v4.4-rc1.
We should really get to it this time in the next few days.
Arnd
next prev parent reply other threads:[~2015-12-06 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 16:21 [GIT PULL] LPC32xx DTS changes for v4.4 Vladimir Zapolskiy
2015-11-29 13:48 ` Vladimir Zapolskiy
2015-12-06 11:36 ` Vladimir Zapolskiy
2015-12-06 19:50 ` Arnd Bergmann [this message]
2015-12-10 16:46 ` 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=3112069.RxjfiMKgHG@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