From: Petr Mladek <pmladek@suse.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jessica Yu <jeyu@redhat.com>, Miroslav Benes <mbenes@suse.cz>
Subject: Re: [PATCH v6] Livepatch shadow variables
Date: Mon, 25 Sep 2017 17:45:48 +0200 [thread overview]
Message-ID: <20170925154548.GA13820@pathway.suse.cz> (raw)
In-Reply-To: <nycvar.YFH.7.76.1709141408100.4703@jbgna.fhfr.qr>
On Thu 2017-09-14 14:08:35, Jiri Kosina wrote:
> On Thu, 31 Aug 2017, Joe Lawrence wrote:
>
> > This version cleans up a few minor tweaks requested by Josh and
> > Miroslav.
> >
> > v6:
> >
> > - Convert an enum into a function argument flag
> > - Update code comment that still referenced updating existing shadow
> > variables
> > - Doc: Add a closing ')' parenthesis character
> > - Doc: Add a blurb about callers providing mutual exclusion
> >
> > Joe Lawrence (1):
> > livepatch: introduce shadow variable API
>
> Applied to for-4.15/shadow-variables, so please send any followup fixes on
> top of that branch.
JFYI, v6 in for-4.15/shadow-variables branch looks great to me.
I have only sent 2 small fixes for the documentation in a separate
patch. Feel free to squash it into the original patch if you want.
Also feel free to use for the original patch:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Best Regards,
Petr
prev parent reply other threads:[~2017-09-25 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 20:37 [PATCH v6] Livepatch shadow variables Joe Lawrence
2017-08-31 20:37 ` [PATCH v6] livepatch: introduce shadow variable API Joe Lawrence
2017-09-12 16:20 ` Josh Poimboeuf
2017-09-12 22:11 ` Joe Lawrence
2017-09-13 13:45 ` Jiri Kosina
2017-09-13 12:00 ` Miroslav Benes
2017-09-14 21:08 ` [PATCH v6] Livepatch shadow variables Jiri Kosina
2017-09-25 15:45 ` Petr Mladek [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=20170925154548.GA13820@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
/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).