From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755478AbcANXl7 (ORCPT ); Thu, 14 Jan 2016 18:41:59 -0500 Received: from devils.ext.ti.com ([198.47.26.153]:37239 "EHLO devils.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752555AbcANXl5 (ORCPT ); Thu, 14 Jan 2016 18:41:57 -0500 Subject: Re: [PATCH v2 9/9] regulator: add LM363X driver To: Mark Brown 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> CC: , , , , , From: "Kim, Milo" Message-ID: <5698323B.4030401@ti.com> Date: Fri, 15 Jan 2016 08:41:47 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20160114102736.GP6588@sirena.org.uk> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@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