[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b280db0e-f1f7-41b5-887c-3b7b847ba035@nvidia.com>
Date: Wed, 7 Jan 2026 08:41:22 +0200
From: Gal Pressman <gal@...dia.com>
To: Feng Tang <feng.tang@...ux.alibaba.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>, Petr Mladek
<pmladek@...e.com>, linux-kernel@...r.kernel.org,
Mark Bloch <mbloch@...dia.com>, Nimrod Oren <noren@...dia.com>
Subject: Re: [PATCH] panic: only warn about deprecated panic_print on write
access
On 07/01/2026 5:00, Feng Tang wrote:
>> @@ -1014,7 +1015,6 @@ static int panic_print_set(const char *val, const struct kernel_param *kp)
>>
>> static int panic_print_get(char *val, const struct kernel_param *kp)
>> {
>> - panic_print_deprecated();
>
> Actually this was intentional, in one of the patch version, this
> panic_print_get() was not there but reusing the param_get_ulong().
>
> It was added later as sometimes developer do want to runtime check
> the current 'panic_print' setting through /sys/module/kernel/parameters/
> interface, and I thought it may be better to give the warning.
I figured it would make sense to keep the behaviors consistent.
Powered by blists - more mailing lists