From mboxrd@z Thu Jan 1 00:00:00 1970 From: "tj@kernel.org" Subject: Re: linux-next: Tree for Jul 25 (ahci_imx.c) Date: Fri, 26 Jul 2013 07:18:50 -0400 Message-ID: <20130726111850.GD30786@mtj.dyndns.org> References: <20130725151253.8b9b53b3a3cf6cacd501dc54@canb.auug.org.au> <51F16F17.4030002@infradead.org> <0E83723C55F66F43A6041464FE31119D3487F2@039-SN2MPN1-011.039d.mgd.msft.net> <20130726040349.GA29268@S2101-09.ap.freescale.net> <0E83723C55F66F43A6041464FE31119D34886A@039-SN2MPN1-011.039d.mgd.msft.net> <20130726052519.GB29268@S2101-09.ap.freescale.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20130726052519.GB29268@S2101-09.ap.freescale.net> Sender: linux-kernel-owner@vger.kernel.org To: Shawn Guo Cc: Zhu Richard-R65037 , Randy Dunlap , Stephen Rothwell , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-ide@vger.kernel.org" List-Id: linux-ide@vger.kernel.org On Fri, Jul 26, 2013 at 01:25:21PM +0800, Shawn Guo wrote: > On Fri, Jul 26, 2013 at 04:58:14AM +0000, Zhu Richard-R65037 wrote: > > Hi Shawn: > > yes, it is. > > > > BTW, Should I re-send the AHCI_IMX patch-set or send out one stand-alone patch to fix this issue? > > > > I think an incremental fixing patch is good. Yeap, it's already upstream. There's no other way. Thanks. -- tejun