linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/8] arm: dts: lpc32xx: updates to LPC32xx SoC and boards
Date: Sun, 08 Nov 2015 17:39:51 +0200	[thread overview]
Message-ID: <563F6CC7.3050704@mleia.com> (raw)
In-Reply-To: <3973745.SoYxz6UFdV@wuerfel>

Hi Arnd,

On 21.10.2015 17:45, Arnd Bergmann wrote:
> On Sunday 18 October 2015 00:35:49 Vladimir Zapolskiy wrote:
>> The change improves description of NXP LPC32xx hardware, among
>> important changes it adds standard timers and external memory
>> controller nodes, splits PWM device node into two,
>>
>> Changes from v1 to v2:
>> - removed v1 2/5 "arm: dts: lpc32xx: fix improper usage of ranges property"
>> - v1 4/5 "arm: dts: lpc32xx: remove unneeded cell settings from cpus"
>>   is replaced by v2 3/8 "arm: dts: lpc32xx: add reg property to cpu device node"
>> - new change, sets physical memory offset for EA3250 and PHY3250 v5/8
>> - new change, added EMC device node v2 6/8
>> - new change, added standard timer nodes v2 7/8
>> - new change, grouped USB subdevices together v2 8/8
> 
> Looks ok to me. Who should pick them up? I haven't seen pull requests from
> Roland in a while. If he's still interested in the port, I think it would be
> best if he could create a branch here.
> 
> If not, we can pick them up directly this time into arm-soc, but then we
> should find a new maintainer.
> 
> 	Arnd 

please pick this series up for v4.3, if it is still possible.

Thank you.

--
With best wishes,
Vladimir

  parent reply	other threads:[~2015-11-08 15:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 21:35 [PATCH v2 0/8] arm: dts: lpc32xx: updates to LPC32xx SoC and boards Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 1/8] arm: dts: lpc32xx: change include syntax to be C preprocessor friendly Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 2/8] arm: dts: lpc32xx: add labels to all defined peripheral nodes Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 3/8] arm: dts: lpc32xx: add reg property to cpu device node Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 4/8] arm: dts: lpc32xx: add device node for the second pwm controller Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 5/8] arm: dts: ea3250/phy3250: specify phys memory offset for lpc32xx boards Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 6/8] arm: dts: lpc32xx: add external memory controller device node Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 7/8] arm: dts: lpc32xx: add device nodes for standard timers Vladimir Zapolskiy
2015-10-17 21:41   ` [PATCH v3 " Vladimir Zapolskiy
2015-10-17 21:35 ` [PATCH v2 8/8] arm: dts: lpc32xx: move USB controller subdevices into own device node Vladimir Zapolskiy
2015-11-20 19:47   ` Rob Herring
2015-11-20 20:05     ` Vladimir Zapolskiy
2015-10-21 14:45 ` [PATCH v2 0/8] arm: dts: lpc32xx: updates to LPC32xx SoC and boards Arnd Bergmann
2015-10-29 22:06   ` Vladimir Zapolskiy
2015-11-08 15:39   ` Vladimir Zapolskiy [this message]
2015-11-13 20:20     ` Vladimir Zapolskiy
2015-11-13 21:16       ` 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=563F6CC7.3050704@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).