From: bryan.wu@canonical.com (Bryan Wu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v9 00/19] Introduce a led trigger for CPU activity and consolidate LED driver in ARM
Date: Thu, 10 May 2012 08:17:17 +0800 [thread overview]
Message-ID: <CAK5ve-Lu+RhY2vj7EnsgLNt8_wMEt_X66c8nHYDPbd2YJ28bcQ@mail.gmail.com> (raw)
In-Reply-To: <1336607530.2494.111.camel@ted>
On Thu, May 10, 2012 at 7:52 AM, Richard Purdie <rpurdie@rpsys.net> wrote:
> On Thu, 2012-05-10 at 07:41 +0800, Bryan Wu wrote:
>> On Thu, May 10, 2012 at 4:38 AM, Arnd Bergmann <arnd.bergmann@linaro.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.
>>
>> > In the long run,
>> > it would be nice to have a proper maintainer for this again after Richard
>> > more or less stepped down from that position. Given that Bryan has shown
>> > that he's persistent enough to get this patch series to v9, how about
>> > making him the primary maintainer for the entire subsystem? He should
>> > know a lot about it already. Bryan?
>> >
>>
>> I do love to start to do more contribution and maintain the
>> drivers/leds subsystem with Richard's help, if Richard is fine with
>> this, I can send out patch to add a MAINTAINER entry.
>
> I'm ok with that, I'm also happy to stay involved at a distance. I do
> read emails and try and help where I can :). I'm just not doing day to
> day rebuilds of cutting edge kernels so the patch work isn't something
> I've been able to find time for and the Yocto Project is where my main
> focus appears best placed at the moment.
>
Thanks, Richard, I really appreciate your help here
-Bryan
prev parent reply other threads:[~2012-05-10 0:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 15:01 [PATCH v9 00/19] Introduce a led trigger for CPU activity and consolidate LED driver in ARM Bryan Wu
2012-05-01 15:01 ` [PATCH 01/19] led-triggers: rename *trigger to *trig for unified naming scheme Bryan Wu
2012-05-01 15:01 ` [PATCH 02/19] led-triggers: create a trigger for CPU activity Bryan Wu
2012-05-01 16:05 ` Tim Gardner
2012-05-01 15:01 ` [PATCH 03/19] ARM: at91: convert old leds drivers to gpio_led and led_trigger drivers Bryan Wu
2012-05-01 15:01 ` [PATCH 04/19] ARM: mach-realview and mach-versatile: retire custom LED code Bryan Wu
2012-05-01 15:01 ` [PATCH 05/19] ARM: mach-ks8695: remove leds driver, since nobody use it Bryan Wu
2012-05-01 15:01 ` [PATCH 06/19] ARM: mach-shark: retire custom LED code Bryan Wu
2012-05-01 15:01 ` [PATCH 07/19] ARM: mach-orion5x: convert custom LED code to gpio_led and LED CPU trigger Bryan Wu
2012-05-01 15:01 ` [PATCH 08/19] ARM: mach-integrator: move CM_CTRL to header file for accessing by other functions Bryan Wu
2012-05-01 15:01 ` [PATCH 09/19] ARM: mach-integrator: retire custom LED code Bryan Wu
2012-05-01 15:01 ` [PATCH 10/19] ARM: mach-clps711x: retire custom LED code of P720T machine Bryan Wu
2012-05-01 15:01 ` [PATCH 11/19] ARM: mach-ebsa110: retire custom LED code Bryan Wu
2012-05-01 15:01 ` [PATCH 12/19] ARM: mach-footbridge: " Bryan Wu
2012-05-01 15:01 ` [PATCH 13/19] char: nwflash: remove old led event code Bryan Wu
2012-05-01 15:01 ` [PATCH 14/19] ARM: mach-pxa: retire custom LED code Bryan Wu
2012-05-01 15:01 ` [PATCH 15/19] ARM: plat-samsung: remove including old leds event API header file Bryan Wu
2012-05-01 15:01 ` [PATCH 16/19] ARM: mach-pnx4008: " Bryan Wu
2012-05-01 15:01 ` [PATCH 17/19] ARM: mach-omap1: retire custom LED code Bryan Wu
2012-05-01 15:01 ` [PATCH 18/19] ARM: mach-sa1100: " Bryan Wu
2012-05-01 15:01 ` [PATCH 19/19] ARM: use new LEDS CPU trigger stub to replace old one Bryan Wu
2012-05-08 17:45 ` [PATCH v9 00/19] Introduce a led trigger for CPU activity and consolidate LED driver in ARM Bryan Wu
2012-05-08 19:19 ` Andrew Morton
2012-05-09 16:16 ` Bryan Wu
2012-05-09 19:24 ` Andrew Morton
2012-05-09 20:38 ` Arnd Bergmann
2012-05-09 23:41 ` Bryan Wu
2012-05-09 23:47 ` Olof Johansson
2012-05-10 0:15 ` Bryan Wu
2012-05-10 1:25 ` Nicolas Pitre
2012-05-10 17:38 ` Bryan Wu
2012-05-10 18:01 ` Nicolas Pitre
2012-05-10 18:11 ` Andrew Morton
2012-05-11 23:11 ` Bryan Wu
2012-05-12 14:53 ` Arnd Bergmann
2012-05-13 7:06 ` Olof Johansson
2012-05-18 12:43 ` Bryan Wu
2012-05-18 15:31 ` Olof Johansson
2012-05-09 23:52 ` Richard Purdie
2012-05-10 0:17 ` Bryan Wu [this message]
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=CAK5ve-Lu+RhY2vj7EnsgLNt8_wMEt_X66c8nHYDPbd2YJ28bcQ@mail.gmail.com \
--to=bryan.wu@canonical.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).