linux-kernel - Re: [PATCHv2 -next] LEDS: LED module of DA9052 PMIC driver

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] [day] [month] [year] [list]

Message-ID: <20110518221542.GB20909@sirena.org.uk>
Date:	Wed, 18 May 2011 23:15:42 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ashish Jangam <Ashish.Jangam@...tcummins.com>,
	Lars-Peter Clausen <lars@...afoo.de>,
	"rpurdie@...ys.net" <rpurdie@...ys.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Dajun Chen <Dajun.Chen@...semi.com>
Subject: Re: [PATCHv2 -next] LEDS: LED module of DA9052 PMIC driver

On Wed, May 18, 2011 at 12:23:32PM -0700, Andrew Morton wrote:

> A way to proceed with this patchset is to get the core PMIC_DA9052
> support patch merged and to then send the various dependent patches to
> the relevant maintainers.

...

> An alternative way of getting it all merged up is for us to ask Samuel
> to merge _all_ the patches, after receiving suitable acks and reviews
> from suitable people.  Or I can do that.

> I think the second way is better.  Sam?

The way these things have often been dealt with is to just merge the
code via the various trees and rely on -next for build testing - they
won't cause bisection issues as the lack of the MFD will prevent the
config being enabled, everything goes in in a single release and we
still get to keep all the code for each subsystem together.

Of course, since the code isn't even signed off we've got a way to go
yet...
--
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/