From: Greg KH <gregkh@linuxfoundation.org>
To: Miroslav Benes <mbenes@suse.cz>
Cc: stable@vger.kernel.org, alexander.levin@microsoft.com,
jkosina@suse.cz, jpoimboe@redhat.com, nstange@suse.de,
pmladek@suse.com, stable-commits@vger.kernel.org
Subject: Re: Patch "livepatch: Initialize shadow variables safely by a custom callback" has been added to the 4.16-stable tree
Date: Thu, 21 Jun 2018 03:50:49 +0900 [thread overview]
Message-ID: <20180620185049.GC32326@kroah.com> (raw)
In-Reply-To: <alpine.LSU.2.21.1806190953110.22815@pobox.suse.cz>
On Tue, Jun 19, 2018 at 09:56:05AM +0200, Miroslav Benes wrote:
> On Sun, 17 Jun 2018, gregkh@linuxfoundation.org wrote:
>
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > livepatch: Initialize shadow variables safely by a custom callback
> >
> > to the 4.16-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > livepatch-initialize-shadow-variables-safely-by-a-custom-callback.patch
> > and it can be found in the queue-4.16 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> Hi,
>
> I think the patch really should not be added to the stable tree. It is not
> a bug fix. It is a new feature. The original API was more limited and this
> patch extends it.
>
> The same applies to patch "livepatch: Allow to call a custom callback when
> freeing shadow variables".
Now dropped, thanks for letting me know.
greg k-h
prev parent reply other threads:[~2018-06-20 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15292346244498@kroah.com>
2018-06-19 7:56 ` Patch "livepatch: Initialize shadow variables safely by a custom callback" has been added to the 4.16-stable tree Miroslav Benes
2018-06-20 18:50 ` Greg KH [this message]
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=20180620185049.GC32326@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alexander.levin@microsoft.com \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=mbenes@suse.cz \
--cc=nstange@suse.de \
--cc=pmladek@suse.com \
--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).