From: Jiri Kosina <jikos@kernel.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>,
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>, Gabriel Gomes <gagomes@suse.com>,
Alice Ferrazzi <alice.ferrazzi@gmail.com>,
Michael Matz <matz@suse.de>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: ulp-devel@opensuse.org, live-patching@vger.kernel.org
Subject: Live patching MC at LPC2020?
Date: Fri, 27 Mar 2020 14:20:52 +0100 (CET) [thread overview]
Message-ID: <nycvar.YFH.7.76.2003271409380.19500@cbobk.fhfr.pm> (raw)
Hi everybody,
oh well, it sounds a bit awkward to be talking about any conference plans
for this year given how the corona things are untangling in the world, but
LPC planning committee has issued (a) statement about Covid-19 (b) call
for papers (as originally planned) nevertheless. Please see:
https://linuxplumbersconf.org/
https://linuxplumbersconf.org/event/7/abstracts/
for details.
Under the asumption that this Covid nuisance is over by that time and
travel is possible (and safe) again -- do we want to eventually submit a
livepatching miniconf proposal again?
I believe there are still kernel related topics on our plate (like revised
handling of the modules that has been agreed on in Lisbon and Petr has
started to work on, the C parsing effort by Nicolai, etc), and at the same
time I'd really like to include the new kids on the block too -- the
userspace livepatching folks (CCing those I know for sure are working on
it).
So, please if you have any opinion one way or the other, please speak up.
Depending on the feedback, I will be fine handling the logistics of the
miniconf submission as last year (together with Josh I guess?) unless
someone else wants to step up and volunter himself :)
(*) which is totally unclear, yes -- for example goverment in my country
has been talking for border closure lasting for 1+ years ... but it
all depends on how things develop of course).
Thanks,
--
Jiri Kosina
SUSE Labs
next reply other threads:[~2020-03-27 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 13:20 Jiri Kosina [this message]
2020-03-30 14:01 ` Live patching MC at LPC2020? Michael Matz
2020-03-31 20:52 ` Joe Lawrence
2020-04-08 10:22 ` Kamalesh Babulal
2020-04-14 10:03 ` Alice ferrazzi
2020-06-25 6:59 ` Petr Mladek
2020-06-27 5:43 ` Alice
2020-06-30 21:45 ` Josh Poimboeuf
2020-07-01 13:13 ` Michael Matz
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=nycvar.YFH.7.76.2003271409380.19500@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=alice.ferrazzi@gmail.com \
--cc=gagomes@suse.com \
--cc=jbaron@akamai.com \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=live-patching@vger.kernel.org \
--cc=matz@suse.de \
--cc=mbenes@suse.cz \
--cc=nstange@suse.com \
--cc=pmladek@suse.com \
--cc=ulp-devel@opensuse.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).