On Wed 10-01-18 11:31:37, Greg KH wrote:
On Wed, Jan 10, 2018 at 11:11:49AM +0100, Libor Pechacek wrote:
Greg,
I appreciate the notifications about patch moves. They make my life easier. However, I don't understand how this change qualified for -stable. The issue does not look serious enough to me to pass the criteria described in Documentation/process/stable-kernel-rules.rst and I don't see which other patch may require this one in v4.4.111.
What is the background for including this patch in -stable, please?
This patch fixes an issue, and was a "good enough" fix that at least one distro has been shipping it in their kernel for a long time. So I figured it would be good for everyone to benifit from the bugfix, not just a tiny subset of the 4.4 kernel users :)
Oh, fairness is a strong argument. However, I'm unhappy to hear that our community is tiny part of Linux user base. ;-)
Hope this helps,
Indeed it does. Thanks!
Libor