[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130726111850.GD30786@mtj.dyndns.org>
Date: Fri, 26 Jul 2013 07:18:50 -0400
From: "tj@...nel.org" <tj@...nel.org>
To: Shawn Guo <shawn.guo@...aro.org>
Cc: Zhu Richard-R65037 <r65037@...escale.com>,
Randy Dunlap <rdunlap@...radead.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>
Subject: Re: linux-next: Tree for Jul 25 (ahci_imx.c)
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
--
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/
Powered by blists - more mailing lists