From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Jessica Yu <jeyu@redhat.com>, Jiri Kosina <jikos@kernel.org>,
Vojtech Pavlik <vojtech@suse.com>,
Miroslav Benes <mbenes@suse.cz>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linuxppc-dev@ozlabs.org, Balbir Singh <bsingharora@gmail.com>,
Torsten Duwe <duwe@suse.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Nikolay Borisov <kernel@kyup.com>
Subject: Re: [PATCH v2] livepatch: Add some basic LivePatch documentation
Date: Tue, 26 Apr 2016 17:13:07 -0500 [thread overview]
Message-ID: <20160426221307.hmtfa7n6uokipwru@treble> (raw)
In-Reply-To: <1461597275-32120-1-git-send-email-pmladek@suse.com>
On Mon, Apr 25, 2016 at 05:14:35PM +0200, Petr Mladek wrote:
> LivePatch framework deserves some documentation, definitely.
> This is an attempt to provide some basic info. I hope that
> it will be useful for both LivePatch producers and also
> potential developers of the framework itself.
>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
My only comment is s/LivePatch/livepatch/ here and in the subject.
Otherwise it looks great to me. Really nice work!
--
Josh
next prev parent reply other threads:[~2016-04-26 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 15:14 [PATCH v2] livepatch: Add some basic LivePatch documentation Petr Mladek
2016-04-26 9:53 ` Balbir Singh
2016-04-27 9:37 ` Miroslav Benes
2016-04-26 11:44 ` Chris J Arges
2016-04-27 20:08 ` Jiri Kosina
2016-04-28 11:19 ` Chris J Arges
2016-04-26 22:13 ` Josh Poimboeuf [this message]
2016-04-27 18:38 ` Jessica Yu
2016-04-27 20:04 ` [PATCH v2] " Jiri Kosina
2016-04-27 20:08 ` Jiri Kosina
2016-04-28 1:46 ` Balbir Singh
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=20160426221307.hmtfa7n6uokipwru@treble \
--to=jpoimboe@redhat.com \
--cc=bsingharora@gmail.com \
--cc=duwe@suse.de \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=kernel@kyup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=live-patching@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mbenes@suse.cz \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=vojtech@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