linux-kernel - Re: [PATCH v9 00/19] Introduce a led trigger for CPU activity and consolidate LED driver in ARM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 May 2012 16:47:01 -0700
From:	Olof Johansson <olof@...om.net>
To:	Bryan Wu <bryan.wu@...onical.com>
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 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.



-Olof
--
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/