From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Kent Overstreet <kent.overstreet@linux.dev>,
linux-kernel@vger.kernel.org
Cc: Luis Chamberlain <mcgrof@kernel.org>,
Petr Pavlu <petr.pavlu@suse.com>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org
Subject: Re: [PATCH] params: Add support for static keys
Date: Tue, 13 May 2025 19:51:57 +0200 [thread overview]
Message-ID: <a4700ad8-1e6d-4f57-b160-e7b6d172ef60@csgroup.eu> (raw)
In-Reply-To: <20250510210126.4032840-1-kent.overstreet@linux.dev>
Le 10/05/2025 à 23:01, Kent Overstreet a écrit :
> Static keys can now be a module parameter, e.g.
>
> module_param_named(foo, foo.key, static_key_t, 0644)
>
> bcachefs is now using this.
>
> Cc: Luis Chamberlain <mcgrof@kernel.org>
> Cc: Petr Pavlu <petr.pavlu@suse.com>
> Cc: Sami Tolvanen <samitolvanen@google.com>
> Cc: Daniel Gomez <da.gomez@samsung.com>
> Cc: linux-modules@vger.kernel.org
> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
> ---
> include/linux/jump_label.h | 2 ++
> include/linux/moduleparam.h | 6 ++++++
> kernel/params.c | 35 +++++++++++++++++++++++++++++++++++
> 3 files changed, 43 insertions(+)
>
> diff --git a/include/linux/jump_label.h b/include/linux/jump_label.h
> index fdb79dd1ebd8..0fc9b71db56f 100644
> --- a/include/linux/jump_label.h
> +++ b/include/linux/jump_label.h
> @@ -107,6 +107,8 @@ struct static_key {
> #endif /* CONFIG_JUMP_LABEL */
> };
>
> +typedef struct static_key static_key_t;
> +
Please read https://docs.kernel.org/process/coding-style.html#typedefs
I can't see the reason for a new typedef here. If there is a valid
reason please explain in the commit message.
Christophe
next prev parent reply other threads:[~2025-05-13 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 21:01 Kent Overstreet
2025-05-12 13:51 ` Petr Pavlu
2025-05-13 13:06 ` Kent Overstreet
2025-05-13 17:51 ` Christophe Leroy [this message]
2025-05-14 16:56 ` Kent Overstreet
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=a4700ad8-1e6d-4f57-b160-e7b6d172ef60@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=da.gomez@samsung.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.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
all inboxes | Powered by JetHome®