linux-kernel - Re: [stable] [109/136] USB: xhci: Make TRB completion code comparison readable.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 2 Oct 2009 10:35:47 -0700
From:	Greg KH <gregkh@...e.de>
To:	David Vrabel <david.vrabel@....com>
Cc:	Greg KH <greg@...ah.com>,
	Sarah Sharp <sarah.a.sharp@...ux.intel.com>,
	linux-kernel@...r.kernel.org, stable@...nel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	stable-review@...nel.org, alan@...rguk.ukuu.org.uk
Subject: Re: [stable] [109/136] USB: xhci: Make TRB completion code
 comparison readable.

On Fri, Oct 02, 2009 at 06:23:03PM +0100, David Vrabel wrote:
> Greg KH wrote:
> > 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@...ux.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?
> 
> I have now, sorry.  It just seemed odd that XHCI patches where added to
> stable releases whilst essential WHCI patches don't even make it into
> the current rc tree.

The WHCI patches were submitted much after the XHCI patches.  The XHCI
patches were in my tree, and the -next and -mm patches for weeks, it was
my fault that they didn't make it to Linus earlier.  This is quite
different from the WHCI patches.

thanks,

greg k-h
--
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/