From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: rtatiya@codeaurora.org,
Robert Ancell <robert.ancell@canonical.com>,
Alan Stern <stern@rowland.harvard.edu>,
"mathias.nyman@linux.intel.com" <mathias.nyman@linux.intel.com>,
chasemetzger15@gmail.com, baolu.lu@linux.intel.com,
oneukum@suse.com, kborer@gmail.com, jun.li@freescale.com,
USB list <linux-usb@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v4.2-rc1 Regression] usb: Enable LPM for USB 2.01+ full-speed devices
Date: Fri, 24 Jun 2016 08:06:45 -0400 [thread overview]
Message-ID: <576D2255.5000703@canonical.com> (raw)
In-Reply-To: <20160622161449.GA27573@kroah.com>
On 06/22/2016 12:14 PM, Greg KH wrote:
> On Wed, Jun 22, 2016 at 11:38:43AM -0400, Joseph Salisbury wrote:
>> Hi Rupesh,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>> commit a8425292816ceaa8c49e29d2114e85d85a73e080
>> Author: Rupesh Tatiya <rtatiya@codeaurora.org>
>> Date: Tue Apr 14 16:36:55 2015 +0530
>>
>> usb: Enable LPM for USB 2.01+ full-speed devices
>>
>>
>> The regression was introduced as of v4.2-rc1.
>>
>> I was hoping to get your feedback, since you are the patch author. Do
>> you think gathering any additional data will help diagnose this issue,
>> or would it be best to submit a revert request?
> Does the problem still happen with 4.7-rc4 or even 4.6?
>
> 4.2 is pretty old and obsolete you know :)
>
> thanks,
>
> greg k-h
The regression does exist in 4.6-rc2. I'll have the latest mainline
4.7-rc4 kernel tested.
next prev parent reply other threads:[~2016-06-24 12:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 15:38 [v4.2-rc1 Regression] usb: Enable LPM for USB 2.01+ full-speed devices Joseph Salisbury
2016-06-22 16:14 ` Greg KH
2016-06-24 12:06 ` Joseph Salisbury [this message]
2016-06-28 15:09 ` Joseph Salisbury
2016-06-28 15:40 ` Alan Stern
2016-06-28 15:44 ` Joseph Salisbury
2016-07-06 20:27 ` Joseph Salisbury
2016-06-22 16:30 ` 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=576D2255.5000703@canonical.com \
--to=joseph.salisbury@canonical.com \
--cc=baolu.lu@linux.intel.com \
--cc=chasemetzger15@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jun.li@freescale.com \
--cc=kborer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=oneukum@suse.com \
--cc=robert.ancell@canonical.com \
--cc=rtatiya@codeaurora.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).