From: Greg KH <gregkh@suse.de>
To: Alexander Holler <holler@ahsoftware.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Felipe Balbi <balbi@ti.com>,
Michael Jones <michael.jones@matrix-vision.de>,
Kernel development list <linux-kernel@vger.kernel.org>,
stable@kernel.org, stable-review@kernel.org,
torvalds@linux-foundation.org,
Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
USB list <linux-usb@vger.kernel.org>,
linux-omap@vger.kernel.org
Subject: Re: [024/115] USB: prevent buggy hubs from crashing the USB stack
Date: Thu, 24 Feb 2011 10:24:24 -0800 [thread overview]
Message-ID: <20110224182424.GA19191@suse.de> (raw)
In-Reply-To: <4D669F56.4020303@ahsoftware.de>
On Thu, Feb 24, 2011 at 07:11:34PM +0100, Alexander Holler wrote:
> Hello,
>
> Am 24.02.2011 18:57, schrieb Alan Stern:
>
> >It's important that this patch appear in .37-stable at the same time as
> >the $SUBJECT patch. If that means delaying $SUBJECT for one release,
> >so be it -- it was not a very important change.
>
> Too late, 2.6.37.1 is already broken. But the patch could be still
> applied to 2.6.32-longterm, at least the message I've replied to
> asked about objections for that version.
It's too late for that release as well, as it's already included in the
last .32 stable release. I'll revert it there also for now.
thanks,
greg k-h
next prev parent reply other threads:[~2011-02-24 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D64C81B.5060807@ahsoftware.de>
2011-02-23 15:26 ` [024/115] USB: prevent buggy hubs from crashing the USB stack Alan Stern
2011-02-24 8:57 ` Felipe Balbi
2011-02-24 9:15 ` Alexander Holler
[not found] ` <4D6621AB.10205-SXC+2es9fhnfWeYVQQPykw@public.gmane.org>
2011-02-24 9:16 ` Felipe Balbi
2011-02-24 17:18 ` Greg KH
2011-02-24 17:23 ` Felipe Balbi
2011-02-24 17:57 ` Alan Stern
2011-02-24 18:11 ` Alexander Holler
2011-02-24 18:24 ` Greg KH [this message]
2011-02-24 18:12 ` Greg KH
2011-02-24 18:16 ` Greg KH
2011-02-24 9:53 ` Michael Jones
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=20110224182424.GA19191@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=balbi@ti.com \
--cc=holler@ahsoftware.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jones@matrix-vision.de \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
/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