Date: Fri, 2 Oct 2009 09:53:16 -0700
From: Greg KH <greg@kroah.com>
To: David Vrabel <david.vrabel@csr.com>
Cc: Greg KH <gregkh@suse.de>, Sarah Sharp <sarah.a.sharp@linux.intel.com>,
       linux-kernel@vger.kernel.org, stable@kernel.org,
       akpm@linux-foundation.org, torvalds@linux-foundation.org,
       stable-review@kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: [stable] [109/136] USB: xhci: Make TRB completion code
 comparison readable.
Message-ID: <20091002165316.GB3890@kroah.com>
References: <20091002011548.335611824@mini.kroah.org>
 <20091002012424.339883108@mini.kroah.org>
 <4AC62C8C.4060906@csr.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AC62C8C.4060906@csr.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1044
Lines: 28

On Fri, Oct 02, 2009 at 05:38:36PM +0100, David Vrabel wrote:
> Greg KH wrote:
> > 2.6.31-stable review patch.  If anyone has any objections, please let us know.
> > 
> > ------------------
> > From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
> > 
> > commit 66d1eebce5cca916e0b08d961690bb01c64751ef upstream.
> > 
> > Use trb_comp_code instead of getting the completion code from the transfer
> > event every time.
> 
> Are all these xhci patches really candidates for the stable tree?  XHCI
> support is marked as EXPERIMENTAL, the xhci standard is still at the
> draft stage, and I don't believe there are any xhci products available
> on the market yet.

Did you read the 000/136 message where I explained why I was accepting
all of these xhci patches into the -stable tree?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/