linux-kernel - Re: [PATCH 2/2] regulator: tps6586x: add support for input supply

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]

Message-ID: <500DBA1F.7050605@wwwdotorg.org>
Date:	Mon, 23 Jul 2012 14:54:55 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Laxman Dewangan <ldewangan@...dia.com>,
	"ccross@...roid.com" <ccross@...roid.com>,
	"olof@...om.net" <olof@...om.net>, "lrg@...com" <lrg@...com>,
	"thierry.reding@...onic-design.de" <thierry.reding@...onic-design.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
	"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>
Subject: Re: [PATCH 2/2] regulator: tps6586x: add support for input supply

On 07/15/2012 03:21 PM, Mark Brown wrote:
> On Fri, Jul 13, 2012 at 10:45:12PM +0530, Laxman Dewangan wrote:
> 
>> I was thinking that 1/2 should also go through your tree to
>> avoid any functionality break on existing platform who are using
>> this regulator.
> 
> I'd be happy to do that if the ARM people are happy with it; just
> let me know and resend the patch if you want me to apply it.

Patch 2/2 really depends on patch 1/2 to avoid git bisect breakage;
are you able to rebase it to maintain that order when applying it?


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