From: Petr Mladek <pmladek@suse.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Joe Lawrence <joe.lawrence@redhat.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Easwar Hariharan <eahariha@linux.microsoft.com>,
live-patching@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 03/10] samples/livepatch: add module descriptions
Date: Tue, 25 Mar 2025 11:01:51 +0100 [thread overview]
Message-ID: <Z-J--iv8LzgArWAX@pathway.suse.cz> (raw)
In-Reply-To: <20250324173242.1501003-3-arnd@kernel.org>
On Mon 2025-03-24 18:32:28, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> Every module should have a description, so add one for each of these modules.
>
> --- a/samples/livepatch/livepatch-callbacks-busymod.c
> +++ b/samples/livepatch/livepatch-callbacks-busymod.c
> @@ -56,4 +56,5 @@ static void livepatch_callbacks_mod_exit(void)
>
> module_init(livepatch_callbacks_mod_init);
> module_exit(livepatch_callbacks_mod_exit);
> +MODULE_DESCRIPTION("Live patching demo for (un)patching callbacks");
This is another support module similar to livepatch-callbacks-mod.c.
I would use the same description, here:
MODULE_DESCRIPTION("Live patching demo for (un)patching callbacks, support module");
> MODULE_LICENSE("GPL");
> diff --git a/samples/livepatch/livepatch-callbacks-demo.c b/samples/livepatch/livepatch-callbacks-demo.c
> index 11c3f4357812..9e69d9caed25 100644
> --- a/samples/livepatch/livepatch-callbacks-demo.c
> +++ b/samples/livepatch/livepatch-callbacks-demo.c
> @@ -192,5 +192,6 @@ static void livepatch_callbacks_demo_exit(void)
>
> module_init(livepatch_callbacks_demo_init);
> module_exit(livepatch_callbacks_demo_exit);
> +MODULE_DESCRIPTION("Live patching demo for (un)patching callbacks");
> MODULE_LICENSE("GPL");
> MODULE_INFO(livepatch, "Y");
> diff --git a/samples/livepatch/livepatch-callbacks-mod.c b/samples/livepatch/livepatch-callbacks-mod.c
> index 2a074f422a51..d1851b471ad9 100644
> --- a/samples/livepatch/livepatch-callbacks-mod.c
> +++ b/samples/livepatch/livepatch-callbacks-mod.c
> @@ -38,4 +38,5 @@ static void livepatch_callbacks_mod_exit(void)
>
> module_init(livepatch_callbacks_mod_init);
> module_exit(livepatch_callbacks_mod_exit);
> +MODULE_DESCRIPTION("Live patching demo for (un)patching callbacks, support module");
> MODULE_LICENSE("GPL");
The rest looks good. With the above change:
Reviewed-by: Petr Mladek <pmladek@suse.com>
Thanks a lot for fixing this.
Arnd, should I push this via the livepatch tree or would you prefer to push
the entire patchset together? Both ways work for me.
Best Regards,
Petr
next prev parent reply other threads:[~2025-03-25 10:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 17:32 [PATCH 01/10] exportfs: add module description Arnd Bergmann
2025-03-24 17:32 ` [PATCH 02/10] ASN.1: " Arnd Bergmann
2025-04-06 18:21 ` Geert Uytterhoeven
2025-03-24 17:32 ` [PATCH 03/10] samples/livepatch: add module descriptions Arnd Bergmann
2025-03-25 10:01 ` Petr Mladek [this message]
2025-03-25 15:03 ` Jeff Johnson
2025-03-24 17:32 ` [PATCH 04/10] fpga: tests: " Arnd Bergmann
2025-03-25 17:06 ` Marco Pagani
2025-04-25 4:27 ` Xu Yilun
2025-03-24 17:32 ` [PATCH 05/10] xenbus: add module description Arnd Bergmann
2025-03-27 16:43 ` Jürgen Groß
2025-03-24 17:32 ` [PATCH 06/10] zlib: " Arnd Bergmann
2025-03-24 17:32 ` [PATCH 07/10] ucs2_string: " Arnd Bergmann
2025-03-24 17:32 ` [PATCH 08/10] kunit: add module description for backtrace suppression test Arnd Bergmann
2025-03-24 17:32 ` [PATCH 09/10] mm/kasan: add module decription Arnd Bergmann
2025-03-24 22:00 ` Andrey Konovalov
2025-03-24 17:32 ` [PATCH 10/10] kunit: slub: add module description Arnd Bergmann
2025-03-25 14:58 ` (subset) [PATCH 01/10] exportfs: " Christian Brauner
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=Z-J--iv8LzgArWAX@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=eahariha@linux.microsoft.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mbenes@suse.cz \
--cc=sfr@canb.auug.org.au \
/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