From: Lance Yang <lance.yang@linux.dev>
To: Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Steven Rostedt <rostedt@goodmis.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, paulmck@kernel.org,
john.ogness@linutronix.de, kernel test robot <lkp@intel.com>,
Feng Tang <feng.tang@linux.alibaba.com>
Subject: Re: [PATCH v2] panic: Clean up message about deprecated 'panic_print' parameter
Date: Wed, 20 Aug 2025 19:03:13 +0800 [thread overview]
Message-ID: <df3b5c81-eb26-41ec-a27b-28c273a74859@linux.dev> (raw)
In-Reply-To: <aKWYELPjbhC7R8NO@pathway.suse.cz>
On 2025/8/20 17:40, Petr Mladek wrote:
> Remove duplication of the message about deprecated 'panic_print'
> parameter.
>
> Also make the wording more direct. Make it clear that the new
> parameters already exist and should be used instead.
>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
Confirmed that it fixes the build error when CONFIG_SYSCTL is
disabled.
Tested-by: Lance Yang <lance.yang@linux.dev>
next prev parent reply other threads:[~2025-08-20 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aKRJKZHgcxyNF3y7@pathway.suse.cz>
2025-08-20 1:31 ` [PATCH] panic: Clean up message about deprecated 'panic_print' parameter kernel test robot
2025-08-20 1:54 ` Lance Yang
2025-08-20 1:56 ` Lance Yang
2025-08-20 8:57 ` Lance Yang
2025-08-20 9:33 ` Petr Mladek
2025-08-20 9:40 ` [PATCH v2] " Petr Mladek
2025-08-20 11:03 ` Lance Yang [this message]
2025-08-25 1:01 ` Feng Tang
2025-08-20 10:39 ` [PATCH] " Lance Yang
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=df3b5c81-eb26-41ec-a27b-28c273a74859@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=feng.tang@linux.alibaba.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
/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;
as well as URLs for NNTP newsgroup(s).