From: Josh Poimboeuf <jpoimboe@redhat.com>
To: live-patching@vger.kernel.org
Cc: Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>, Nicolai Stange <nstange@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Jason Baron <jbaron@akamai.com>,
Alice Ferrazzi <alice.ferrazzi@gmail.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: [Linux Plumbers Conference] Please submit your livepatch LPC topic proposals by Monday
Date: Fri, 2 Aug 2019 15:42:24 -0500 [thread overview]
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:
https://www.linuxplumbersconf.org/event/4/page/34-accepted-microconferences#lpatch
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:
https://www.linuxplumbersconf.org/login/?next=%2Fevent%2F4%2Fabstracts%2F%23submit-abstract
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.
Thanks!
--
Josh
reply other threads:[~2019-08-02 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190802204224.ochmshq2pzler7ms@treble \
--to=jpoimboe@redhat.com \
--cc=alice.ferrazzi@gmail.com \
--cc=jbaron@akamai.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=nstange@suse.com \
--cc=pmladek@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