From mboxrd@z Thu Jan 1 00:00:00 1970 From: nicolas.pitre@linaro.org (Nicolas Pitre) Date: Wed, 9 May 2012 21:25:21 -0400 (EDT) Subject: [PATCH v9 00/19] Introduce a led trigger for CPU activity and consolidate LED driver in ARM In-Reply-To: References: <1335884506-15370-1-git-send-email-bryan.wu@canonical.com> <20120509122436.1b612004.akpm@linux-foundation.org> <201205092038.16722.arnd.bergmann@linaro.org> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, 10 May 2012, Bryan Wu wrote: > On Thu, May 10, 2012 at 7:47 AM, Olof Johansson wrote: > > On Wed, May 9, 2012 at 4:41 PM, Bryan Wu wrote: > >> On Thu, May 10, 2012 at 4:38 AM, Arnd Bergmann wrote: > >>> On Wednesday 09 May 2012, Andrew Morton wrote: > >>>> I'm the LEDs patchmonkey at present. ?I can merge the drivers/leds > >>>> change if you like, but there doesn't seem much point in that unless > >>>> all the other patches get merged. > >>>> > >>>> So my preferred approach would be for the patch series to get merged > >>>> via some ARM tree. > >>> > >>> I'm fine with taking it through arm-soc if that helps. > >> > >> That would be great to merge from arm-soc tree, thanks a lot, Arnd and Andrew. > > > > Ok, cool. Do you want to stage a branch in a git repo that we pull, or > > do you prefer that we pick up the patches as posted? It's easier for > > us to just do a pull but either way is fine. > > > > Great, I've already put in my kernel tree > > Please find these patches here: > git://kernel.ubuntu.com/roc/linux-2.6/.git leds You applied your patches on top of linux-next. This can't be merged upstream until you rebase your patches on something stable such as pure v3.4-rc6 for example. Nicolas