On Fri, Oct 15, 2021 at 09:54:45AM +0200, Greg KH wrote: > On Fri, Oct 15, 2021 at 01:29:20AM -0500, braewoods@xxxxxxxxxxxxx wrote: > > On 2021-10-13 21:20, Alan Stern wrote: > > > In the future, you should always include a version number in the email > > > Subject: line (for example, "[PATCH v2]") so that readers will know > > > which patch is which. And you should include, here just below the "---" > > > line, a description of how this version differs from the previous > > > version. See the email archives for examples of multi-version patches. > > > > > > Nevertheless, this looks okay. > > > > > > Acked-by: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> > > > > Noted. I'll do that for future patches. On a side note, any idea how long it > > normally takes to get a simple patch like this committed? I've had mixed > > experiences with getting feedback on patches. Sometimes my patches just get > > totally ignored. > > Depends on the subsystem and the patch submitted. Greg tends to be quite good at merging patches in a timely manner. They generally are committed within a few weeks. In this case, should the patch also be added to the -stable kernels? Alan Stern > Also always use scripts/get_maintainer.pl to properly copy the needed > maintainers and mailing lists. Sometimes patches get lost in the noise > if the right people are not copied. > > thanks, > > greg k-h
