From: Petr Mladek <pmladek@suse.com>
To: Song Liu <song@kernel.org>
Cc: live-patching@vger.kernel.org, linux-kernel@vger.kernel.org,
jpoimboe@kernel.org, jikos@kernel.org, mbenes@suse.cz,
joe.lawrence@redhat.com
Subject: Re: [PATCH v3 1/2] livepatch: add sysfs entry "patched" for each klp_object
Date: Fri, 23 Sep 2022 16:59:06 +0200 [thread overview]
Message-ID: <Yy3JupD4iErp0daR@alley> (raw)
In-Reply-To: <20220902205208.3117798-2-song@kernel.org>
On Fri 2022-09-02 13:52:07, Song Liu wrote:
> Add per klp_object sysfs entry "patched". It makes it easier to debug
> typos in the module name.
>
> Reviewed-by: Joe Lawrence <joe.lawrence@redhat.com>
> Signed-off-by: Song Liu <song@kernel.org>
Just a note. Signed-off-by of the author is always the first entry.
It is followed by Acked-by, Reviewed-by, Tested-by, ... in the order
in which they arrived.
I have fixed the ordering when pushing the patch.
> --- a/Documentation/ABI/testing/sysfs-kernel-livepatch
> +++ b/Documentation/ABI/testing/sysfs-kernel-livepatch
> @@ -55,6 +55,14 @@ Description:
> The object directory contains subdirectories for each function
> that is patched within the object.
>
> +What: /sys/kernel/livepatch/<patch>/<object>/patched
> +Date: August 2022
> +KernelVersion: 6.0.0
Also I have updated the version to 6.1.0. It should be the version
produced by the upcoming merge window.
Best Regards,
Petr
next prev parent reply other threads:[~2022-09-23 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 20:52 [PATCH v3 0/2] add sysfs entry "patched" for each klp_object Song Liu
2022-09-02 20:52 ` [PATCH v3 1/2] livepatch: " Song Liu
2022-09-23 14:59 ` Petr Mladek [this message]
2022-09-02 20:52 ` [PATCH v3 2/2] selftests/livepatch: add sysfs test Song Liu
2022-09-23 14:50 ` [PATCH v3 0/2] add sysfs entry "patched" for each klp_object 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=Yy3JupD4iErp0daR@alley \
--to=pmladek@suse.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=song@kernel.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