From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Kim, Milo" Subject: Re: [PATCH v2 9/9] regulator: add LM363X driver Date: Fri, 15 Jan 2016 08:41:47 +0900 Message-ID: <5698323B.4030401@ti.com> References: <1448521025-2796-1-git-send-email-milo.kim@ti.com> <1448521025-2796-10-git-send-email-milo.kim@ti.com> <56975493.7050900@ti.com> <20160114102736.GP6588@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20160114102736.GP6588@sirena.org.uk> Sender: linux-leds-owner@vger.kernel.org To: Mark Brown Cc: lee.jones@linaro.org, robh+dt@kernel.org, j.anaszewski@samsung.com, devicetree@vger.kernel.org, linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org 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