On Sun, Jul 28, 2019 at 01:25:32PM +0200, Maik Stohn wrote: > Hello Greg, > > Sorry to trouble you again. > > I was waiting and observing how the FIX is applied and it looks like > it will not be applied to 5.2.x (5.2.3 and 5.2.4 came out without this > patch). > Personally I think it is a big mistake not to merge the fix but this > is your decision. > > I have to tell my users now to AVOID KERNEL 5.2 at all since it is > buggy and most likely will never be fixed. > > But since it is also not part of any 5.3 (right now) I'm a bit afraid > I also need to put a warning to avoid 5.3 as well. > > Would be nice to get an official statement like: "Linux kernel will > not merge the USB fix to 5.2, maybe 5.3 will have it, but better wait > for 5.4", so I can quote this to my users. How about an official statement like "wait a week please" :) Or, "if you have problems, please apply this patch." We _just_ found the fix, it _just_ went into my tree a few days ago. A patch can not be in a stable kernel until it shows up in Linus's kernel, in a release (like a -rc). So, ideally this patch gets into 5.3-rc2. Then I can add it to the queue of patches to go into the 5.2.y release, which should happen sometime next week or the week after at worst case. Please read Documentation/process/ for how all of this works if you are curious, we have tests to pass, releases to make it through, and reviews to happen here. Give us a chance please, there is no major rush. And if there is a rush, you have the fix to apply to your kernel to solve the problem! You are not dependant on any of us here anymore, anyone can patch their machines if they run into this issue and can not wait a week or so. Also, odds are that most people are even running the 5.2.y kernel yet is pretty low... :) So, again, patience. Your fix is just one of hundreds winding its way through the ether to get out to users. You are not alone, and at the same time, not special. It will happen, just relax. greg k-h
