From: Bradley Morgan <brads@mainlining.org>
To: feng.tang@linux.alibaba.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
pmladek@suse.com
Subject: Re: [PATCH] panic: remove the unneeded panic_print_get()
Date: Wed, 02 Sep 2026 13:28:24 +0100 [thread overview]
Message-ID: <3B7DFEB5-70C0-4CAD-9C68-A7EB7D297606@mainlining.org> (raw)
In-Reply-To: <20260902114851.77062-1-feng.tang@linux.alibaba.com>
On 2 September 2026 12:48:51 BST, Feng Tang <feng.tang@linux.alibaba.com>
wrote:
Feng!
>panic_print_get() was introduced in commit 2683df6539cb ("panic: add
>note that 'panic_print' parameter is deprecated") to print out warning
>message of the deprecation of 'panic_print' on read access.
>
>Since commit 90f3c123247e ("panic: only warn about deprecated panic_print
>on write access"), panic_print_get() wrapper is not needed anymore for
>read access, so remove it and use param_get_ulong() instead.
>
could you say that this is only a cleanup?
Reviewed-by: Bradley Morgan <brads@mainlining.org>
>Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com>
>---
> kernel/panic.c | 7 +------
> 1 file changed, 1 insertion(+), 6 deletions(-)
>
>diff --git a/kernel/panic.c b/kernel/panic.c
>index 7dda841c16f9..50715f14cf04 100644
>--- a/kernel/panic.c
>+++ b/kernel/panic.c
>@@ -1216,14 +1216,9 @@ static int panic_print_set(const char *val, const struct kernel_param *kp)
> return param_set_ulong(val, kp);
> }
>
>-static int panic_print_get(char *val, const struct kernel_param *kp)
>-{
>- return param_get_ulong(val, kp);
>-}
>-
> static const struct kernel_param_ops panic_print_ops = {
> .set = panic_print_set,
>- .get = panic_print_get,
>+ .get = param_get_ulong,
Ack.
> };
> __core_param_cb(panic_print, &panic_print_ops, &panic_print, 0644);
>
>
--- Thanks!
https://lore.kernel.org/all/EE579805-42F2-4C58-B752-F28779EEB717@grrlz.net/
next prev parent reply other threads:[~2026-09-02 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 11:48 Feng Tang
2026-09-02 12:28 ` Bradley Morgan [this message]
2026-09-03 14:01 ` 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=3B7DFEB5-70C0-4CAD-9C68-A7EB7D297606@mainlining.org \
--to=brads@mainlining.org \
--cc=akpm@linux-foundation.org \
--cc=feng.tang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®