mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gal Pressman <gal@nvidia.com>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Petr Mladek <pmladek@suse.com>,
	linux-kernel@vger.kernel.org, Mark Bloch <mbloch@nvidia.com>,
	Nimrod Oren <noren@nvidia.com>
Subject: Re: [PATCH] panic: only warn about deprecated panic_print on write access
Date: Wed, 7 Jan 2026 08:41:22 +0200	[thread overview]
Message-ID: <b280db0e-f1f7-41b5-887c-3b7b847ba035@nvidia.com> (raw)
In-Reply-To: <aV3MWf005ja00BDU@U-2FWC9VHC-2323.local>

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.

  reply	other threads:[~2026-01-07  6:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 16:33 Gal Pressman
2026-01-07  3:00 ` Feng Tang
2026-01-07  6:41   ` Gal Pressman [this message]
2026-01-07  7:20     ` Feng Tang
2026-01-08 15:52       ` Petr Mladek
2026-01-11  8:28         ` Gal Pressman
2026-01-12  3:32           ` Feng Tang
2026-01-12  6:48             ` Gal Pressman
2026-01-12 15:03               ` 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=b280db0e-f1f7-41b5-887c-3b7b847ba035@nvidia.com \
    --to=gal@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=feng.tang@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=noren@nvidia.com \
    --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®