linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Joseph Salisbury <joseph.salisbury@canonical.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	LKML <linux-kernel@vger.kernel.org>, <pkondeti@codeaurora.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	Herton Krzesinski <herton.krzesinski@canonical.com>,
	<stable@vger.kernel.org>, <linux-usb@vger.kernel.org>
Subject: Re: [REVERT][v3.x.y] EHCI: Update qTD next pointer in QH overlay region during unlink
Date: Thu, 17 Jan 2013 13:56:39 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1301171353330.1339-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <50F84441.8080300@canonical.com>

On Thu, 17 Jan 2013, Joseph Salisbury wrote:

> Hello,
> 
> Please consider reverting commit 
> 3d037774b42ed677f699b1dce7d548d55f4e4c2b in mainline as well as in the 
> current stable releases.  It was included upstream as of v3.6-rc6.  This 
> commit introduced a regression, described in the following bug report:
> 
> http://bugs.launchpad.net/bugs/1088733
> 
> Reverting commit 3d037774b42ed677f699b1dce7d548d55f4e4c2b in the v3.2 
> kernel has been confirmed to resolve the aforementioned bug.

I do not want to revert this commit without first understanding what is 
going wrong.  Please ask the reporter to post usbmon traces showing 
what happens in both a failed and a successful recording attempt.

Alan Stern


  parent reply	other threads:[~2013-01-17 18:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 18:34 [REVERT][v3.x.y] EHCI: Update qTD next pointer in QH overlay region during unlink Joseph Salisbury
2013-01-17 18:51 ` Ben Hutchings
2013-01-17 18:53   ` Joseph Salisbury
2013-01-17 18:56 ` Alan Stern [this message]
2013-01-17 19:30   ` Joseph Salisbury
2013-02-01 22:51   ` Joseph Salisbury
2013-02-04 22:04     ` Alan Stern
2013-02-05 15:53       ` Joseph Salisbury
2013-02-05 16:36         ` Alan Stern
2013-02-06 23:27       ` Joseph Salisbury

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.44L0.1301171353330.1339-100000@iolanthe.rowland.org \
    --to=stern@rowland.harvard.edu \
    --cc=ben@decadent.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=herton.krzesinski@canonical.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pkondeti@codeaurora.org \
    --cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).