live-patching.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Joe Lawrence <joe.lawrence@redhat.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Miroslav Benes <mbenes@suse.cz>, Petr Mladek <pmladek@suse.com>,
	Nicolai Stange <nstange@suse.com>,
	Jason Baron <jbaron@akamai.com>, Gabriel Gomes <gagomes@suse.com>,
	Alice Ferrazzi <alice.ferrazzi@gmail.com>,
	Michael Matz <matz@suse.de>,
	ulp-devel@opensuse.org, live-patching@vger.kernel.org
Subject: Re: Live patching MC at LPC2020?
Date: Wed, 8 Apr 2020 15:52:59 +0530	[thread overview]
Message-ID: <57a1a529-3afb-988e-f5a8-f979d8a1fe12@linux.vnet.ibm.com> (raw)
In-Reply-To: <20200331205204.GA7388@redhat.com>

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:
>>
>> 	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).
>>
> 
> 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)

Hi Jiri,

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.
> 

Regards,
Kamalesh


  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

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=57a1a529-3afb-988e-f5a8-f979d8a1fe12@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=alice.ferrazzi@gmail.com \
    --cc=gagomes@suse.com \
    --cc=jbaron@akamai.com \
    --cc=jikos@kernel.org \
    --cc=joe.lawrence@redhat.com \
    --cc=jpoimboe@redhat.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).