From: Joe Lawrence <joe.lawrence@redhat.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Jiri Kosina <jikos@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Miroslav Benes <mbenes@suse.cz>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
Nicolai Stange <nstange@suse.de>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC 3/5] livepatch: Allow to distinguish different version of system state changes
Date: Fri, 21 Jun 2019 11:00:08 -0400 [thread overview]
Message-ID: <20190621142156.GF20356@redhat.com> (raw)
In-Reply-To: <20190621140911.GC20356@redhat.com>
On Fri, Jun 21, 2019 at 10:09:11AM -0400, Joe Lawrence wrote:
> More word play: would it be any clearer to drop the use of
> "modification" when talking about klp_states? Sometimes I read
> modification to mean a change to a klp_state itself rather than the
> system at large.
After reading through the rest of the series, maybe I was premature
about this. "System state modification" is used consistently throughout
the series, so without having any better suggestion, ignore my comment.
-- Joe
next prev parent reply other threads:[~2019-06-21 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190611135627.15556-1-pmladek@suse.com>
2019-06-21 13:19 ` [RFC 0/5] livepatch: new API to track system state changes Joe Lawrence
[not found] ` <20190611135627.15556-3-pmladek@suse.com>
2019-06-21 13:43 ` [RFC 2/5] livepatch: Basic " Joe Lawrence
2019-06-24 9:32 ` Nicolai Stange
[not found] ` <20190611135627.15556-5-pmladek@suse.com>
2019-06-21 14:15 ` [RFC 4/5] livepatch: Documentation of the new API for tracking " Joe Lawrence
[not found] ` <20190611135627.15556-6-pmladek@suse.com>
2019-06-21 11:54 ` [RFC 5/5] livepatch: Selftests of the " Miroslav Benes
2019-06-21 14:19 ` Joe Lawrence
2019-06-24 9:27 ` [RFC 0/5] livepatch: new API to track " Nicolai Stange
[not found] ` <20190611135627.15556-4-pmladek@suse.com>
2019-06-21 11:27 ` [RFC 3/5] livepatch: Allow to distinguish different version of " Miroslav Benes
2019-06-21 14:09 ` Joe Lawrence
2019-06-21 15:00 ` Joe Lawrence [this message]
2019-06-24 10:26 ` Nicolai Stange
2019-07-18 11:38 ` Petr Mladek
2019-07-18 9:08 ` Petr Mladek
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=20190621142156.GF20356@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=jikos@kernel.org \
--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 \
--cc=pmladek@suse.com \
/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).