linux-kernel - Re: [PATCH v2 9/9] regulator: add LM363X 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 for Android: free password hash cracker in your pocket

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

Message-ID: <5698323B.4030401@ti.com>
Date:	Fri, 15 Jan 2016 08:41:47 +0900
From:	"Kim, Milo" <milo.kim@...com>
To:	Mark Brown <broonie@...nel.org>
CC:	<lee.jones@...aro.org>, <robh+dt@...nel.org>,
	<j.anaszewski@...sung.com>, <devicetree@...r.kernel.org>,
	<linux-leds@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 9/9] regulator: add LM363X driver

On 1/14/2016 7:27 PM, Mark Brown wrote:
> On Thu, Jan 14, 2016 at 04:56:03PM +0900, Milo Kim wrote:
>
>> So, I'd like to know which is better for you.
>> a) Create a patch based on linux-next tree (the above patch)
>> Or
>> b) Re-generate a patch based on linux-mfd tree
>
> At this point the easiest thing might be to wait for v4.5-rc1 then send
> a patch for that after everything gets merged.

OK, thanks!

Best regards,
Milo