ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Jiri Kosina <jkosina@suse.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] live patching
Date: Mon, 12 Oct 2015 13:13:52 -0400	[thread overview]
Message-ID: <20151012171352.GD31035@thunk.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1507071253390.10183@pobox.suse.cz>

I'd like to ask folks whether they feel we still need further
discussion on Live Patching at the kernel summit.  Not being present
at the Live Kernel Patching miniconf, if folks could describe what
issues still need to be resolved or discussed, I'd really appreciate
it.

Thanks,

					- Ted

  parent reply	other threads:[~2015-10-12 17:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 20:42 Jiri Kosina
2015-07-08 16:13 ` Masami Hiramatsu
2015-07-08 21:21   ` Jiri Kosina
2015-07-09  3:26   ` Kamezawa Hiroyuki
2015-07-09  9:56     ` Jiri Kosina
2015-07-09 10:05       ` Kamezawa Hiroyuki
2015-10-12 17:13 ` Theodore Ts'o [this message]
2015-10-13  9:29   ` Jiri Kosina
2015-10-16 19:34     ` Jiri Kosina

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=20151012171352.GD31035@thunk.org \
    --to=tytso@mit.edu \
    --cc=jkosina@suse.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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