On Tue, Jan 03, 2017 at 12:43:19PM -0600, Bin Liu wrote: > On Tue, Jan 03, 2017 at 07:31:58PM +0100, Greg KH wrote: > > On Tue, Jan 03, 2017 at 11:54:31AM -0600, Bin Liu wrote: > > > On Tue, Jan 03, 2017 at 07:37:18PM +0200, Felipe Balbi wrote: > > > > IOW, since you're Ccing stable, you consider this to be a > > > > regression. Then the question reads as: "Are you missing a 'Fixes: foo > > > > bar baz' in your commit log?" > > > > > > I think it is difficult to find out the commit to blame, so I used 'cc > > > stable' tag, not 'Fixes:...'. Any recommendation for better logging it? > > > > Say in the changelog, "this has been there since the beginning of the > > driver", then you don't need to have a kernel version for the stable > > tag. > > Then all the active stable trees will pick this fix? Yes, they will try to. > 1. so far only am335x reported this issue, and this device is only > several years old, but musb support was added sin 2008. And due to > the hw integration, likely am335x would be the only device have > such issue. > 2. because of the mass in the musb drivers, I am not that comfortable > to get a patch into musb-core in any old kernel unless it can be > tested. Ok, that's your call, if you want to say 4.1+, it is fine with me, as I only care about 4.4 and 4.9 stable kernels :) thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
