From: Mike Isely <isely@isely.net>
To: Greg KH <greg@kroah.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Justin Piszcz <jpiszcz@lucidpixels.com>,
Oliver Neukum <oliver@neukum.org>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Mike Isely at pobox <isely@pobox.com>
Subject: Re: Bug fix for pvrusb2 driver [was: Re: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)]
Date: Thu, 23 Oct 2008 14:54:25 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0810231451080.1475@cnc.isely.net> (raw)
In-Reply-To: <20081023191543.GA10017@kroah.com>
On Thu, 23 Oct 2008, Greg KH wrote:
> On Thu, Oct 23, 2008 at 11:27:11AM -0500, Mike Isely wrote:
> > On Mon, 20 Oct 2008, Greg KH wrote:
> >
[...]
> > >
> > > Will this patch be sent to the -stable group, to fix this regression in
> > > 2.6.27? Or should they take Alan's fix instead?
> > >
> >
> > Greg:
> >
> > I didn't directly answer your question here because I had figured it was
> > answered in a previous post on this thread, that Mike Krufky had already
> > explicitly asked that it be queued (and added his Reviewed-By tag), and
> > that I figured it best not to add yet more noise to an already noisy
> > group.
> >
> > However now I see that this patch didn't get into 2.6.27.3. It's a
> > pretty important fix; without it the pvrusb2 driver is worse than
> > useless (unless one adds initusbreset=0 as a module option).
>
> As we were discussing this on Monday, and the review cycle for 2.6.27.3
> started last Saturday, it would have been pretty hard to get it into
> 2.6.27.3 :)
>
> I need to see the patch in Linus's tree first, before it can go into any
> stable release. Is it in there yet? If so, please send me the git
> commit id and I'll queue it up for the next -stable round.
>
OK, I understand.
As far as I know, Linus has not yet pulled the changes from Mauro (part
of a larger set). But that information is a few hours old. I or Mike
Krufky will let you know if/when one of us finds out.
Thanks for following up.
-Mike
--
Mike Isely
isely @ pobox (dot) com
PGP: 03 54 43 4D 75 E5 CC 92 71 16 01 E2 B5 F5 C1 E8
next prev parent reply other threads:[~2008-10-23 19:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 11:26 Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE) Justin Piszcz
2008-10-19 11:28 ` Justin Piszcz
2008-10-19 15:34 ` Oliver Neukum
2008-10-19 16:51 ` Justin Piszcz
2008-10-20 14:02 ` Alan Stern
2008-10-20 15:21 ` Justin Piszcz
2008-10-20 16:17 ` Bug fix for pvrusb2 driver [was: Re: Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE)] Alan Stern
2008-10-20 16:21 ` Mike Isely
2008-10-20 16:33 ` Justin Piszcz
2008-10-20 16:50 ` Mike Isely
2008-10-20 17:03 ` Justin Piszcz
2008-10-20 17:16 ` Alan Stern
2008-10-20 16:37 ` Mike Isely
2008-10-20 17:29 ` Greg KH
2008-10-20 18:01 ` Michael Krufky
2008-10-23 16:27 ` Mike Isely
2008-10-23 19:15 ` Greg KH
2008-10-23 19:54 ` Mike Isely [this message]
2008-10-23 22:04 ` Michael Krufky
2008-10-23 22:11 ` Justin Piszcz
2008-10-24 5:43 ` Mike Isely
2008-10-24 15:29 ` Michael Krufky
2008-10-24 21:30 ` Greg KH
2008-10-19 15:34 ` Kernel 2.6.26.5 -> 2.6.27.2 [USB REGRESSION] (USB -> D_STATE) Alan Stern
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=Pine.LNX.4.64.0810231451080.1475@cnc.isely.net \
--to=isely@isely.net \
--cc=greg@kroah.com \
--cc=isely@pobox.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).