mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miroslav Benes <mbenes@suse.cz>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Jessica Yu <jeyu@kernel.org>, Jiri Kosina <jikos@kernel.org>,
	Petr Mladek <pmladek@suse.com>,
	Chris J Arges <chris.j.arges@canonical.com>
Subject: Re: [PATCH v2 0/1] add (un)patch callbacks
Date: Tue, 15 Aug 2017 11:00:26 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LSU.2.20.1708151059190.8441@pobox.suse.cz> (raw)
In-Reply-To: <1502220967-21410-1-git-send-email-joe.lawrence@redhat.com>

On Tue, 8 Aug 2017, Joe Lawrence wrote:

> Hi folks,
> 
> This is v2 of the livepatch (un)patch hook/notifier/callback/etc code.
> 
> The documentation is still a little rough, but I wanted to post up the
> code for feedback before getting too far in revising it.
> 
> This implements the pre and post handlers as Josh suggested.  See
> summary of related changes below...
> 
> v2:
> - s/hooks/callbacks/g
> - implemented pre-(un)patch and post-(un)patch callbacks
>   - pre-patch and pre-unpatch callbacks run from callers of
>     klp_patch_object() and klp_unpatch_object()
>   - post-patch and post-unpatch callbacks run from
>     klp_complete_transition() and klp_module_coming/going()
> - reduce callbacks from a list to a single per-klp_object instance
> - revamp the sample callback demo
> - revamp documentation
> 
> Feedback appreciated as always.

Looks almost good to me. v3 with Josh's review should be ok.

Miroslav

      parent reply	other threads:[~2017-08-15  9:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 19:36 Joe Lawrence
2017-08-08 19:36 ` [PATCH v2 1/1] livepatch: " Joe Lawrence
2017-08-11 20:44   ` Josh Poimboeuf
2017-08-14 14:53     ` Joe Lawrence
2017-08-14 17:29       ` Josh Poimboeuf
2017-08-15  9:00 ` Miroslav Benes [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=alpine.LSU.2.20.1708151059190.8441@pobox.suse.cz \
    --to=mbenes@suse.cz \
    --cc=chris.j.arges@canonical.com \
    --cc=jeyu@kernel.org \
    --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=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®