From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] LPC32xx DTS changes for v4.4
Date: Sun, 06 Dec 2015 13:36:43 +0200 [thread overview]
Message-ID: <56641DCB.5080600@mleia.com> (raw)
In-Reply-To: <565B024A.2030704@mleia.com>
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?
Thank you.
With best wishes,
Vladimir
>> ----------------------------------------------------------------
>> Main changes in the series:
>> - Added description of the second PWM controller device
>> - Added External Memory Controller device tree node (Primecell PL175)
>> - Added device tree nodes for standard timer controllers
>> - USB controllers are grouped
>> - Various minor clean-ups needed for further development of LPC32xx
>>
>> ----------------------------------------------------------------
>> Vladimir Zapolskiy (8):
>> arm: dts: lpc32xx: change include syntax to be C preprocessor friendly
>> arm: dts: lpc32xx: add labels to all defined peripheral nodes
>> arm: dts: lpc32xx: add reg property to cpu device node
>> arm: dts: lpc32xx: add device node for the second pwm controller
>> arm: dts: ea3250/phy3250: specify phys memory offset for lpc32xx boards
>> arm: dts: lpc32xx: add external memory controller device node
>> arm: dts: lpc32xx: add device nodes for standard timers
>> arm: dts: lpc32xx: move USB controller subdevices into own device node
>>
>> arch/arm/boot/dts/ea3250.dts | 41 +++++-------
>> arch/arm/boot/dts/lpc32xx.dtsi | 142 ++++++++++++++++++++++++++++++-----------
>> arch/arm/boot/dts/phy3250.dts | 41 +++++-------
>> 3 files changed, 139 insertions(+), 85 deletions(-)
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2015-12-06 11:36 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 [this message]
2015-12-06 19:50 ` Arnd Bergmann
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=56641DCB.5080600@mleia.com \
--to=vz@mleia.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).