From: Balbir Singh <bsingharora@gmail.com>
To: Jiri Kosina <jikos@kernel.org>, Petr Mladek <pmladek@suse.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Jessica Yu <jeyu@redhat.com>, 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, 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: Thu, 28 Apr 2016 11:46:18 +1000 [thread overview]
Message-ID: <57216B6A.20302@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1604272208130.27368@cbobk.fhfr.pm>
On 28/04/16 06:08, Jiri Kosina wrote:
> On Wed, 27 Apr 2016, Jiri Kosina wrote:
>
>> I've incorporated most of the feedback (*) and pushed out to
>> livepatching.git#for-4.7/livepatching-doc so everybody please send any
>> followup documentation patches on top of that branch.
>
> (*) Balbir, some of your comments were a bit too vague; if you could turn
> them into actual patch on top of what's currently in git, that'd be
> helpful
>
Hi, Jiri
Thanks! I'll try to do that -- I'll add it on my TODO list.
Balbir Singh.
prev parent reply other threads:[~2016-04-28 1:46 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
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 [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=57216B6A.20302@gmail.com \
--to=bsingharora@gmail.com \
--cc=duwe@suse.de \
--cc=jeyu@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).