From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Jason Baron <jbaron@akamai.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Evgenii Shatokhin <eshatokhin@virtuozzo.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] livepatch: Followup changes for the atomic replace patchset
Date: Wed, 6 Feb 2019 09:22:37 -0600 [thread overview]
Message-ID: <20190206152237.vhoq2jsz6el2yysq@treble> (raw)
In-Reply-To: <20190204135653.31406-1-pmladek@suse.com>
On Mon, Feb 04, 2019 at 02:56:49PM +0100, Petr Mladek wrote:
> This patchset implements ideas that were mentioned and postponed during
> the review of the atomic replace patchset.
>
> The patches apply on top of livepatching.git, branch
> origin/for-5.1/atomic-replace.
>
>
> Changes against v1:
>
> + Added Joe's patch that fixed ptr_id() error code [Joe]
> + Did proper error handling in the shadow variable sefttest [All]
> + Removed the controversial patch that was removing patch->enabled flag [All].
> + Fixed few typo's [Joe]
> + Added available Acks.
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
--
Josh
prev parent reply other threads:[~2019-02-06 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 13:56 Petr Mladek
2019-02-04 13:56 ` [PATCH v2 1/4] livepatch: Introduce klp_for_each_patch macro Petr Mladek
2019-02-04 13:56 ` [PATCH v2 2/4] livepatch: return -ENOMEM on ptr_id() allocation failure Petr Mladek
2019-02-05 13:26 ` Miroslav Benes
2019-02-04 13:56 ` [PATCH v2 3/4] livepatch: Proper error handling in the shadow variables selftest Petr Mladek
2019-02-05 14:18 ` Miroslav Benes
2019-02-05 21:17 ` Joe Lawrence
2019-02-04 13:56 ` [PATCH v2 4/4] livepatch: Module coming and going callbacks can proceed with all listed patches Petr Mladek
2019-02-06 10:29 ` [PATCH v2 0/4] livepatch: Followup changes for the atomic replace patchset Petr Mladek
2019-02-06 15:22 ` Josh Poimboeuf [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=20190206152237.vhoq2jsz6el2yysq@treble \
--to=jpoimboe@redhat.com \
--cc=eshatokhin@virtuozzo.com \
--cc=jbaron@akamai.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.com \
/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
all inboxes | Powered by JetHome®