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 12:24:36 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Bryan Wu <bryan.wu@...onical.com>
Cc:	linux@....linux.org.uk, rpurdie@...ys.net,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linus.walleij@...aro.org, arnd.bergmann@...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, 10 May 2012 00:16:14 +0800
Bryan Wu <bryan.wu@...onical.com> wrote:

> On Wed, May 9, 2012 at 3:19 AM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> > On Wed, 9 May 2012 01:45:43 +0800
> > Bryan Wu <bryan.wu@...onical.com> wrote:
> >
> >> Any comments and suggestions about my v9 patchset.
> >
> > The drivers/leds/ changes look OK to me.
> 
> Thanks a lot, Andrew.
> Richard, what about merging this driver firstly in drivers/leds/?
> 

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.



Failing that, I can merge them all myself.  Acks from ARM maintainers
and from maintainers of arm-specific drivers are very desirable, but I
wouldn't be surprised if few are forthcoming.

If nothing happens over the next week or so, please remind me (or resend
the patch series) and I'll suck them in.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ