From: Kamalesh Babulal <firstname.lastname@example.org>
To: Jiri Kosina <email@example.com>
Cc: Joe Lawrence <firstname.lastname@example.org>,
Josh Poimboeuf <email@example.com>,
Miroslav Benes <firstname.lastname@example.org>, Petr Mladek <email@example.com>,
Nicolai Stange <firstname.lastname@example.org>,
Jason Baron <email@example.com>, Gabriel Gomes <firstname.lastname@example.org>,
Alice Ferrazzi <email@example.com>,
Michael Matz <firstname.lastname@example.org>,
Subject: Re: Live patching MC at LPC2020?
Date: Wed, 8 Apr 2020 15:52:59 +0530 [thread overview]
Message-ID: <email@example.com> (raw)
On 4/1/20 2:22 AM, Joe Lawrence wrote:
> On Fri, Mar 27, 2020 at 02:20:52PM +0100, Jiri Kosina wrote:
>> 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:
>> 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
> Hi Jiri,
> First off, I hope everyone is riding out COVID-19 as well as possible,
> considering all that's happening.
> As for LPC mini-conf topics, I'd be interested in (at least):
> - Petr's per-object livepatch POC
> - klp-convert status
> - objtool hacking
> - Nicolai's klp-ccp status
> - arch update (arm64, etc)
I hope everyone is keeping safe. I would be interested in the topics listed
by Joe and in userspace patching.
>> 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).
> Hmm, all good points. Some conferences have gone virtual to cope with
> necessary cancellations, but who knows what things will look like even
> at the end of August. Perhaps we can still do something remotely if the
> conditions dictate it. But my vote would be yes, and let's see what
> topics interest folks.
next prev parent reply other threads:[~2020-04-08 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-27 13:20 Live patching MC at LPC2020? Jiri Kosina
2020-03-30 14:01 ` Michael Matz
2020-03-31 20:52 ` Joe Lawrence
2020-04-08 10:22 ` Kamalesh Babulal [this message]
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).