Live-Patching Archive on
 help / color / Atom feed
From: Josh Poimboeuf <>
Cc: Jiri Kosina <>, Miroslav Benes <>,
	Petr Mladek <>, Nicolai Stange <>,
	Joe Lawrence <>,
	Jason Baron <>,
	Alice Ferrazzi <>,
	Kamalesh Babulal <>
Subject: [Linux Plumbers Conference] Please submit your livepatch LPC topic proposals by Monday
Date: Fri, 2 Aug 2019 15:42:24 -0500
Message-ID: <20190802204224.ochmshq2pzler7ms@treble> (raw)

[ Steven informed me that my original subject looked like spam and he
  almost deleted it.  He has a point.  Resending with a new subject
  which is less likely to induce email delete trigger finger. ]

Hi all,

Sorry for the late notice, but the CfP for LPC microconference topics is
rapidly approaching.  In fact, I just realized the deadline is
officially today, but they're giving us until Monday.

This year, each presenter is supposed to submit their proposal on the
LPC web site.  Here's what we initially proposed:

     5 min Intro - What happened in kernel live patching over the last year
     API for state changes made by callbacks [1][2]
     source-based livepatch creation tooling [3][4]
     klp-convert [5][6]
     livepatch developers guide
     userspace live patching

If one of those topics is yours, or even if you have something else
you'd like to present/discuss, please go ahead and submit a proposal.  I
think this is the link for submitting:

When planning your talk, please consider Steven Rostedt's sage advice:

  Please avoid presentations. There's not much time per topic thus the
  time spent on a topic needs to be efficient. Slides are allowed, but
  any presentation should only be used to help bring the audience up to
  speed on what you want to accomplish. Focus only on the necessary
  details to allow folks to participate. This should take no more than 5
  minutes (7 tops, but that's stretching it). The important point is
  that slides should be only used to complement a discussion. They
  should not be used to present a new feature or product unless it is
  absolutely necessary for the discussion at hand. All slides and
  "presentations" should be used to help the discussion that follows.

When selecting topics, Jiri and I will prioritize those topics which are
more discussion-based.



                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190802204224.ochmshq2pzler7ms@treble \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Live-Patching Archive on

Archives are clonable:
	git clone --mirror live-patching/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 live-patching live-patching/ \
	public-inbox-index live-patching

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone