public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: avorontsov@ru.mvista.com, Alan Stern <stern@rowland.harvard.edu>,
	David Brownell <dbrownell@users.sourceforge.net>,
	Timur Tabi <timur@freescale.com>, Li Yang <leoli@freescale.com>,
	linux-usb@vger.kernel.org, linuxppc-dev@ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/3] USB: FHCI: Driver should be responsible for managing endpoint queues
Date: Wed, 24 Dec 2008 12:58:35 -0800	[thread overview]
Message-ID: <20081224205835.GA14844@kroah.com> (raw)
In-Reply-To: <20081224121853.b46e9174.akpm@linux-foundation.org>

On Wed, Dec 24, 2008 at 12:18:53PM -0800, Andrew Morton wrote:
> On Wed, 24 Dec 2008 23:08:45 +0300 Anton Vorontsov <avorontsov@ru.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.

I do intend to merge it, given that it's in a buildable format :)

So a merged version would be good for me.

thanks,

greg k-h

  parent reply	other threads:[~2008-12-24 20:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-23 21:03 [PATCH] USB: Driver for Freescale QUICC Engine USB Host Controller Anton Vorontsov
2008-12-23 21:28 ` Andrew Morton
2008-12-24 19:11   ` Anton Vorontsov
2008-12-24  2:45 ` Alan Stern
2008-12-24 19:11   ` Anton Vorontsov
2008-12-24 19:13 ` [PATCH -mm 1/3] USB: FHCI: Driver should be responsible for managing endpoint queues Anton Vorontsov
2008-12-24 19:59   ` Greg KH
2008-12-24 20:08     ` Anton Vorontsov
2008-12-24 20:18       ` Andrew Morton
2008-12-24 20:53         ` [PATCH v2] USB: Driver for Freescale QUICC Engine USB Host Controller Anton Vorontsov
2008-12-24 20:58         ` Greg KH [this message]
2008-12-24 21:07           ` [PATCH -mm 1/3] USB: FHCI: Driver should be responsible for managing endpoint queues Anton Vorontsov
2008-12-24 22:54   ` Alan Stern
2008-12-24 19:13 ` [PATCH -mm 2/3] USB: FHCI: Fix namespace pollution Anton Vorontsov
2008-12-24 19:13 ` [PATCH -mm 3/3] USB: FHCI: Fix memory leaks in fhci_mem_{init,free} Anton Vorontsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081224205835.GA14844@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=leoli@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=stern@rowland.harvard.edu \
    --cc=timur@freescale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox