From: Seth Jennings <sjenning@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jkosina@suse.cz>, Vojtech Pavlik <vojtech@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Petr Mladek <pmladek@suse.cz>, Miroslav Benes <mbenes@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
Andy Lutomirski <luto@amacapital.net>,
live-patching@vger.kernel.org, x86@kernel.org, kpatch@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 0/3] Kernel Live Patching
Date: Tue, 18 Nov 2014 08:42:05 -0600 [thread overview]
Message-ID: <20141118144205.GB1944@cerebellum.variantweb.net> (raw)
In-Reply-To: <546B5675.4060902@suse.cz>
On Tue, Nov 18, 2014 at 03:23:49PM +0100, Jiri Slaby wrote:
> On 11/17/2014, 03:54 PM, Seth Jennings wrote:
> > On Mon, Nov 17, 2014 at 02:33:02PM +0900, Masami Hiramatsu wrote:
> >> Hmm, btw, "LP" and "LPC" remind me line-printer and LPC bus :(
> >> Can we use LKP (Live Kernel Patching) or KLP (Kernel Live Patching) instead ?
> >
> > Jiri S also mentioned this so I guess it is a common sentiment :) He
> > suggested "lip" but I think I like "klp" better? Jiri S sound good?
>
> Definitely, I like both lkp and klp.
Great. I'll make the change.
Thanks,
Seth
>
> --
> js
> suse labs
> --
> To unsubscribe from this list: send the line "unsubscribe live-patching" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-11-18 14:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 1:29 [PATCHv2 0/3] Kernel Live Patching Seth Jennings
2014-11-17 1:29 ` [PATCHv2 1/3] kernel: add TAINT_LIVEPATCH Seth Jennings
2014-11-17 1:29 ` [PATCHv2 2/3] kernel: add support for live patching Seth Jennings
2014-11-17 18:45 ` Greg KH
2014-11-17 19:13 ` Seth Jennings
2014-11-18 14:11 ` Miroslav Benes
2014-11-18 14:26 ` Seth Jennings
2014-11-18 14:45 ` Miroslav Benes
2014-11-19 20:34 ` Seth Jennings
2014-11-20 13:22 ` Miroslav Benes
2014-11-19 15:27 ` Miroslav Benes
2014-11-19 16:05 ` Seth Jennings
2014-11-20 13:10 ` Miroslav Benes
2014-11-20 17:35 ` Josh Poimboeuf
2014-11-20 19:56 ` Seth Jennings
2014-11-21 14:41 ` Miroslav Benes
2014-11-21 14:38 ` Miroslav Benes
2014-11-20 15:19 ` Josh Poimboeuf
2014-11-20 16:48 ` Seth Jennings
2014-11-17 1:29 ` [PATCHv2 3/3] kernel: add sysfs documentation " Seth Jennings
2014-11-17 18:50 ` Greg KH
2014-11-17 5:33 ` [PATCHv2 0/3] Kernel Live Patching Masami Hiramatsu
2014-11-17 13:16 ` Steven Rostedt
2014-11-17 14:54 ` Seth Jennings
2014-11-18 14:23 ` Jiri Slaby
2014-11-18 14:42 ` Seth Jennings [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=20141118144205.GB1944@cerebellum.variantweb.net \
--to=sjenning@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=jslaby@suse.cz \
--cc=kpatch@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
--cc=vojtech@suse.cz \
--cc=x86@kernel.org \
/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).