Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-20 Thread Peter Chen
On Fri, Mar 18, 2016 at 04:01:51PM -0700, Linus Torvalds wrote: > On Fri, Mar 18, 2016 at 3:51 PM, Linus Torvalds > wrote: > > > > The commit that ends up being marked bad is odd, but there it is: > > 69bec7259853 "USB: core: let USB device know device node". > > Confirmed. Not only did it bisect

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-19 Thread Linus Torvalds
On Fri, Mar 18, 2016 at 3:51 PM, Linus Torvalds wrote: > > The commit that ends up being marked bad is odd, but there it is: > 69bec7259853 "USB: core: let USB device know device node". Confirmed. Not only did it bisect to that, reverting it on top of the current kernel fixes my machine. So that

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-19 Thread Linus Torvalds
On Wed, Mar 16, 2016 at 5:09 PM, Greg KH wrote: > > USB patches for 4.6-rc1 > > Here is the big USB patchset for 4.6-rc1. Something in this - or possibly the tty pull, but that doesn't sound very likely - has killed my USB keyboard on my desktop. I'm bisecting right now. Expect a likely revert.

[GIT PULL] USB driver patches for 4.6-rc1

2016-03-19 Thread Greg KH
The following changes since commit fc77dbd34c5c99bce46d40a2491937c3bcbd10af: Linux 4.5-rc6 (2016-02-28 08:41:20 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.6-rc1 for you to fetch changes up to ce53bfc4374cada8b64576

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-19 Thread Linus Torvalds
On Fri, Mar 18, 2016 at 2:43 PM, Linus Torvalds wrote: > > Something in this - or possibly the tty pull, but that doesn't sound > very likely - has killed my USB keyboard on my desktop. Yeah, the bisect is now solidly in the usb part. The machine has 00:14.0 USB controller: Intel Corporation Su

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-18 Thread Greg KH
On Fri, Mar 18, 2016 at 04:09:50PM -0700, Linus Torvalds wrote: > On Fri, Mar 18, 2016 at 3:58 PM, Greg KH wrote: > > > > Yes, people did report issues with that yesterday, and I queued up a > > patch for it, it's attached below, but I didn't think it would cause any > > issues with non-OF systems

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-18 Thread Greg KH
On Fri, Mar 18, 2016 at 03:12:15PM -0700, Greg KH wrote: > On Fri, Mar 18, 2016 at 02:58:27PM -0700, Linus Torvalds wrote: > > On Fri, Mar 18, 2016 at 2:43 PM, Linus Torvalds > > wrote: > > > > > > Something in this - or possibly the tty pull, but that doesn't sound > > > very likely - has killed

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-18 Thread Linus Torvalds
On Fri, Mar 18, 2016 at 3:58 PM, Greg KH wrote: > > Yes, people did report issues with that yesterday, and I queued up a > patch for it, it's attached below, but I didn't think it would cause any > issues with non-OF systems either. I wanted to give it a few days > testing in linux-next before se

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-18 Thread Greg KH
On Fri, Mar 18, 2016 at 03:51:34PM -0700, Linus Torvalds wrote: > On Fri, Mar 18, 2016 at 2:58 PM, Linus Torvalds > wrote: > > > > Yeah, the bisect is now solidly in the usb part. > > The commit that ends up being marked bad is odd, but there it is: > 69bec7259853 "USB: core: let USB device know

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-18 Thread Linus Torvalds
On Fri, Mar 18, 2016 at 2:58 PM, Linus Torvalds wrote: > > Yeah, the bisect is now solidly in the usb part. The commit that ends up being marked bad is odd, but there it is: 69bec7259853 "USB: core: let USB device know device node". Very odd, but I tested multiple times: I'm typing this on d883f

Re: [GIT PULL] USB driver patches for 4.6-rc1

2016-03-18 Thread Greg KH
On Fri, Mar 18, 2016 at 02:58:27PM -0700, Linus Torvalds wrote: > On Fri, Mar 18, 2016 at 2:43 PM, Linus Torvalds > wrote: > > > > Something in this - or possibly the tty pull, but that doesn't sound > > very likely - has killed my USB keyboard on my desktop. > > Yeah, the bisect is now solidly i