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@redhat.com>, Jiri Kosina <jikos@kernel.org>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH 3/3] livepatch: add shadow variable sample program
Date: Tue, 13 Jun 2017 13:00:09 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.20.1706131256540.29266@pobox.suse.cz> (raw)
In-Reply-To: <1496341526-19061-4-git-send-email-joe.lawrence@redhat.com>
On Thu, 1 Jun 2017, Joe Lawrence wrote:
> Modify the sample livepatch to demonstrate the shadow variable API.
>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
> ---
> samples/livepatch/livepatch-sample.c | 39 +++++++++++++++++++++++++++++++++++-
> 1 file changed, 38 insertions(+), 1 deletion(-)
Would it make sense to make this our second sample module? I think we
should keep one as simple as possible, and illustrate new features in
separate sample modules.
I'd like to have another one for klp-convert patch set too.
What do you think?
Miroslav
next prev parent reply other threads:[~2017-06-13 11:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 18:25 [PATCH 0/3] livepatch: add shadow variable API Joe Lawrence
2017-06-01 18:25 ` [PATCH 1/3] livepatch: introduce " Joe Lawrence
2017-06-08 16:49 ` Josh Poimboeuf
2017-06-09 15:36 ` Joe Lawrence
2017-06-09 18:34 ` Josh Poimboeuf
2017-06-12 13:49 ` Joe Lawrence
2017-06-14 12:59 ` Petr Mladek
2017-06-14 13:17 ` Josh Poimboeuf
2017-06-14 14:26 ` Petr Mladek
2017-06-19 16:09 ` Miroslav Benes
2017-06-01 18:25 ` [PATCH 2/3] livepatch: add shadow variable documentation Joe Lawrence
2017-06-14 13:10 ` Petr Mladek
2017-06-01 18:25 ` [PATCH 3/3] livepatch: add shadow variable sample program Joe Lawrence
2017-06-09 18:38 ` Josh Poimboeuf
2017-06-09 19:05 ` Joe Lawrence
2017-06-13 11:00 ` Miroslav Benes [this message]
2017-06-13 17:32 ` Joe Lawrence
2017-06-14 7:45 ` Miroslav Benes
2017-06-14 14:21 ` Petr Mladek
2017-06-14 14:57 ` Josh Poimboeuf
2017-06-15 10:59 ` Petr Mladek
2017-06-15 13:49 ` Josh Poimboeuf
[not found] ` <20170615143800.d6f5p5bdm4ueecly@redhat.com>
2017-06-15 15:23 ` Josh Poimboeuf
2017-06-19 16:56 ` Miroslav Benes
2017-06-30 20:32 ` Josh Poimboeuf
2017-07-01 6:53 ` Miroslav Benes
2017-06-14 15:15 ` Joe Lawrence
2017-06-19 16:43 ` Miroslav Benes
2017-06-01 20:05 ` [PATCH 0/3] livepatch: add shadow variable API Jiri Kosina
2017-06-01 20:23 ` Joe Lawrence
2017-06-01 20:32 ` Jiri Kosina
2017-06-13 10:19 ` Miroslav Benes
2017-06-13 17:29 ` Joe Lawrence
2017-06-14 8:02 ` Miroslav Benes
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.1706131256540.29266@pobox.suse.cz \
--to=mbenes@suse.cz \
--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=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®