stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Libor Pechacek <lpechacek@suse.com>
Cc: rusty@rustcorp.com.au, stable@vger.kernel.org,
	stable-commits@vger.kernel.org
Subject: Re: Patch "module: Issue warnings when tainting kernel" has been added to the 4.4-stable tree
Date: Wed, 10 Jan 2018 11:31:37 +0100	[thread overview]
Message-ID: <20180110103137.GA11061@kroah.com> (raw)
In-Reply-To: <20180110101149.kkhtz2xdbojhdzfr@fm.suse.cz>

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 :)

Hope this helps,

greg k-h

  reply	other threads:[~2018-01-10 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 12:52 Patch "module: Issue warnings when tainting kernel" has been added to the 4.4-stable tree gregkh
2018-01-10 10:11 ` Libor Pechacek
2018-01-10 10:31   ` Greg KH [this message]
2018-01-10 12:33     ` Libor Pechacek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180110103137.GA11061@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=lpechacek@suse.com \
    --cc=rusty@rustcorp.com.au \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).