From: Petr Mladek <pmladek@suse.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Nicolai Stange <nstange@suse.de>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
Miroslav Benes <mbenes@suse.de>,
Alice Ferrazzi <alicef@gentoo.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
live-patching@vger.kernel.org
Subject: Re: Live patching MC preliminary schedule
Date: Tue, 27 Aug 2019 13:17:40 +0200 [thread overview]
Message-ID: <20190827111740.ckb6fr5kewjip4a5@pathway.suse.cz> (raw)
In-Reply-To: <nycvar.YFH.7.76.1908271005260.27147@cbobk.fhfr.pm>
On Tue 2019-08-27 10:08:17, Jiri Kosina wrote:
> Hi,
>
> I've created a preliminary schedule of live patching MC at LPC; it can be
> seen here:
>
> https://linuxplumbersconf.org/event/4/sessions/47/#20190911
>
> Please take a look, and let me know in case you'd like to request any
> modification of the schedule.
The schedule looks reasonable to me.
I guess that "Rethinking late module patching" could cause the most
heating discussion. It is great that it is at the beginning.
On the other hand, "API for state changes made by callbacks" might
be pretty short. The v2 patchset has got positive feedback modulo
some cosmetic issues. This slot might help to catch up with
the schedule when necessary.
Best Regards,
Petr
prev parent reply other threads:[~2019-08-27 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 8:08 Live patching MC preliminary schedule Jiri Kosina
2019-08-27 11:17 ` Petr Mladek [this message]
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=20190827111740.ckb6fr5kewjip4a5@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=alicef@gentoo.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.de \
--cc=nstange@suse.de \
/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).