From: Petr Mladek <pmladek@suse.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Joe Lawrence <joe.lawrence@redhat.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Nicolai Stange <nstange@suse.de>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] livepatch: new API to track system state changes
Date: Fri, 1 Nov 2019 13:14:40 +0100 [thread overview]
Message-ID: <20191101121440.kpvtont5mrmet2mq@pathway.suse.cz> (raw)
In-Reply-To: <20191031180650.g4tss4wfksg2bs6a@treble>
On Thu 2019-10-31 13:06:50, Josh Poimboeuf wrote:
> On Wed, Oct 30, 2019 at 04:43:08PM +0100, Petr Mladek wrote:
> > Hi,
> >
> > this is another piece in the puzzle that helps to maintain more
> > livepatches.
> >
> > Especially pre/post (un)patch callbacks might change a system state.
> > Any newly installed livepatch has to somehow deal with system state
> > modifications done be already installed livepatches.
> >
> > This patchset provides a simple and generic API that
> > helps to keep and pass information between the livepatches.
> > It is also usable to prevent loading incompatible livepatches.
> >
> > Changes since v3:
> >
> > + selftests compilation error [kbuild test robot]
> > + fix copyright in selftests [Joe]
> > + used macros for the module names in selftests [Joe]
> > + allow zero state version [Josh]
> > + slightly refactor the code for checking state version [Josh]
> > + fix few typos reported by checkpatch.pl [Petr]
> > + added Acks [Joe]
>
> Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
The patchset has been commited into livepatch.git, branch
for-5.5/system-state.
Best Regards,
Petr
prev parent reply other threads:[~2019-11-01 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 15:43 [PATCH v4 0/5] livepatch: new API to track system state changes Petr Mladek
2019-10-30 15:43 ` [PATCH v4 1/5] livepatch: Keep replaced patches until post_patch callback is called Petr Mladek
2019-10-30 15:43 ` [PATCH v4 2/5] livepatch: Basic API to track system state changes Petr Mladek
2019-10-30 15:43 ` [PATCH v4 3/5] livepatch: Allow to distinguish different version of " Petr Mladek
2019-10-30 15:43 ` [PATCH v4 4/5] livepatch: Documentation of the new API for tracking " Petr Mladek
2019-10-30 15:43 ` [PATCH v4 5/5] livepatch: Selftests of the " Petr Mladek
2019-10-31 18:06 ` [PATCH v4 0/5] livepatch: new API to track " Josh Poimboeuf
2019-11-01 12:14 ` 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=20191101121440.kpvtont5mrmet2mq@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.