From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Jessica Yu <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>,
Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: [PATCH v6 0/3] livepatch callbacks
Date: Tue, 17 Oct 2017 18:33:30 -0500 [thread overview]
Message-ID: <20171017233330.2kcusko5lqwd5pow@treble> (raw)
In-Reply-To: <1507921723-1996-1-git-send-email-joe.lawrence@redhat.com>
On Fri, Oct 13, 2017 at 03:08:40PM -0400, Joe Lawrence wrote:
> Another turn of the livepatch callback crank. This version cleans up
> some minor issues found in v5 and was rebased on top of Jiri's branches
> listed below.
>
> Unfortunately, I didn't have time to test out Petr's suggestion to move
> the pre-patch callback inside klp_patch_object() and the post-unpatch
> callback into klp_unpatch_object()... let me know if this is a
> deal-breaker (I think it would be possible to revisit this later if
> need be.)
>
> Thanks for all the feedback and suggestions thus far!
Looks perfect! I'm hoping we can get this in for the next merge window.
Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
--
Josh
next prev parent reply other threads:[~2017-10-17 23:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 19:08 Joe Lawrence
2017-10-13 19:08 ` [PATCH v6 1/3] livepatch: add (un)patch callbacks Joe Lawrence
2017-10-18 13:05 ` Miroslav Benes
2017-10-13 19:08 ` [PATCH v6 2/3] livepatch: move transition "complete" notice into klp_complete_transition() Joe Lawrence
2017-10-13 19:08 ` [PATCH v6 3/3] livepatch: add transition notices Joe Lawrence
2017-10-17 23:33 ` Josh Poimboeuf [this message]
2017-10-19 8:14 ` [PATCH v6 0/3] livepatch callbacks Jiri Kosina
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=20171017233330.2kcusko5lqwd5pow@treble \
--to=jpoimboe@redhat.com \
--cc=chris.j.arges@canonical.com \
--cc=jeyu@kernel.org \
--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®