[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK5ve-+rCv3s+K6Laie=QaPqqZ4Vk1+irYU6S4MBZSquKrMWtw@mail.gmail.com>
Date: Thu, 10 May 2012 08:15:33 +0800
From: Bryan Wu <bryan.wu@...onical.com>
To: Olof Johansson <olof@...om.net>
Cc: Arnd Bergmann <arnd.bergmann@...aro.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux@....linux.org.uk, rpurdie@...ys.net,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linus.walleij@...aro.org, nicolas.pitre@...aro.org,
tim.gardner@...onical.com
Subject: Re: [PATCH v9 00/19] Introduce a led trigger for CPU activity and
consolidate LED driver in ARM
On Thu, May 10, 2012 at 7:47 AM, Olof Johansson <olof@...om.net> wrote:
> On Wed, May 9, 2012 at 4:41 PM, Bryan Wu <bryan.wu@...onical.com> wrote:
>> On Thu, May 10, 2012 at 4:38 AM, Arnd Bergmann <arnd.bergmann@...aro.org> 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
Thanks,
--
Bryan Wu <bryan.wu@...onical.com>
Kernel Developer +86.186-168-78255 Mobile
Canonical Ltd. www.canonical.com
Ubuntu - Linux for human beings | www.ubuntu.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists