[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081224121853.b46e9174.akpm@linux-foundation.org>
Date: Wed, 24 Dec 2008 12:18:53 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: avorontsov@...mvista.com
Cc: Greg KH <greg@...ah.com>, Alan Stern <stern@...land.harvard.edu>,
David Brownell <dbrownell@...rs.sourceforge.net>,
Timur Tabi <timur@...escale.com>,
Li Yang <leoli@...escale.com>, linux-usb@...r.kernel.org,
linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm 1/3] USB: FHCI: Driver should be responsible for
managing endpoint queues
On Wed, 24 Dec 2008 23:08:45 +0300 Anton Vorontsov <avorontsov@...mvista.com> wrote:
> On Wed, Dec 24, 2008 at 11:59:36AM -0800, Greg KH wrote:
> > On Wed, Dec 24, 2008 at 10:13:03PM +0300, Anton Vorontsov wrote:
> > > Follow these changes for the FHCI driver:
> >
> > Hm, would it just make more sense to respin the whole driver? That way
> > it's never in the tree in a "broken" state?
>
> It's for -mm tree. If I understand -mm workflow correctly, Andrew
> will merge all the fixes into the final patch before sending it to
> you in late -rc0 phase, when various -next git trees (on which this
> driver depend) will be merged into the Linus tree.
>
> Andrew, am I correct?
Yes, that's what I do.
I prefer to see the incremental patches once a patch has had review or
testing, so we can see which bits changed. But if Greg intends to
merge this driver then he'd probably prefer a fresh new patch,
particularly as a) version 1 was only sent yesterday and b) he hasn't
merged version #1.
--
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