From mboxrd@z Thu Jan 1 00:00:00 1970 From: shc_work@mail.ru (Alexander Shiyan) Date: Sat, 17 Aug 2013 08:32:30 +0400 Subject: [PATCH 00/10] ARM: clps711x: Initial DT support / Fixes In-Reply-To: <20130814062900.GA19951@quad.lixom.net> References: <1374172501-26796-1-git-send-email-shc_work@mail.ru> <20130803075442.6d1a418eb60217f7196a25fc@mail.ru> <20130814062900.GA19951@quad.lixom.net> Message-ID: <20130817083230.9ab0aaf04f8c84d42f88c4ce@mail.ru> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, 13 Aug 2013 23:29:00 -0700 Olof Johansson wrote: > On Sat, Aug 03, 2013 at 07:54:42AM +0400, Alexander Shiyan wrote: > > On Thu, 18 Jul 2013 22:34:51 +0400 > > Alexander Shiyan wrote: > > > > > Here is next patchset for the Cirrus Logic CLPS711X target CPUs. > > > The first four patches is a small fixes. The rest is a attempt > > > to add DT support for this subarch. > > > As long as DT support is incomplete (no peripherals), I did not > > > add DTS yet. This is the next step. > > > > > > Alexander Shiyan (10): > > > ARM: clps711x: Remove the special name for the syscon driver > > > ARM: clps711x: Drop fortunet board support > > > ARM: clps711x: autcpu12: Remove incorrect config checking > > > ARM: clps711x: edb7211: Remove extra iotable_init() call > > > ARM: clps711x: Add CLPS711X clk driver > > > ARM: clps711x: Add CLPS711X clocksource driver > > > ARM: clps711x: Add CLPS711X irqchip driver > > > ARM: clps711x: Add CLPS711X cpuidle driver > > > ARM: clps711x: Migrate CLPS711X subarch to the new basic drivers > > > ARM: clps711x: Add initial DT support > > [...] > > > > If there is no objection about "fixes" part of patchset, > > can these parts (1/10-4/10) be applied? > > Thanks. > > Definitely, I'll apply them to fixes-non-critical for 3.12. > > Btw, Kevin Hilman is stepping in to help out with arm-soc maintenance, so > please email arm at kenrel.org, since it's an alias that we are all on. > > Also, I don't know if I've asked this of you before, but for these "smaller" > platforms that don't see quite so much activity, it's easy for us to forget who > wants us to apply patches and who stages branches. So emails like these are > appreciated so we know if you want them applied, or if we'll get a pull request > later. Clarifying in the patch posting if they are for review or for applying > works too. Do you mean always create CC to "arm at ..." for parts [0/xx] or after review period? Thnaks. -- Alexander Shiyan