From: Lance Yang <lance.yang@linux.dev>
To: kernel test robot <lkp@intel.com>, Petr Mladek <pmladek@suse.com>,
Feng Tang <feng.tang@linux.alibaba.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Andrew Morton <akpm@linux-foundation.org>,
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
Subject: Re: [PATCH] panic: Clean up message about deprecated 'panic_print' parameter
Date: Wed, 20 Aug 2025 09:56:05 +0800 [thread overview]
Message-ID: <33a897b4-7d9a-4641-9c7a-07c19bb9cb6f@linux.dev> (raw)
In-Reply-To: <ae9bb2ea-c6e5-4a4b-ae25-aea1d6fe084d@linux.dev>
On 2025/8/20 09:54, Lance Yang wrote:
>
>
> On 2025/8/20 09:31, kernel test robot wrote:
>> Hi Petr,
>>
>> kernel test robot noticed the following build errors:
>>
>>
>>
>> url: https://github.com/intel-lab-lkp/linux/commits/
>> UPDATE-20250819-180717/Feng-Tang/lib-sys_info-handle-sys_info_mask-0-
>> case/20250815-152131
>> base: the 3th patch of https://lore.kernel.org/
>> r/20250815071428.98041-4-feng.tang%40linux.alibaba.com
>> patch link: https://lore.kernel.org/r/
>> aKRJKZHgcxyNF3y7%40pathway.suse.cz
>> patch subject: [PATCH] panic: Clean up message about deprecated
>> 'panic_print' parameter
>> config: i386-buildonly-randconfig-004-20250820 (https://
>> download.01.org/0day-ci/archive/20250820/202508200907.PsZ3geub-
>> lkp@intel.com/config)
>> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project
>> 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
>> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/
>> archive/20250820/202508200907.PsZ3geub-lkp@intel.com/reproduce)
>>
>> If you fix the issue in a separate patch/commit (i.e. not just a new
>> version of
>> the same patch/commit), kindly add following tags
>> | Reported-by: kernel test robot <lkp@intel.com>
>> | Closes: https://lore.kernel.org/oe-kbuild-all/202508200907.PsZ3geub-
>> lkp@intel.com/
>>
>> All errors (new ones prefixed by >>):
>>
>>>> kernel/panic.c:952:2: error: call to undeclared function
>>>> 'panic_print_deprecated'; ISO C99 and later do not support implicit
>>>> function declarations [-Wimplicit-function-declaration]
>> 952 | panic_print_deprecated();
>> | ^
>> kernel/panic.c:958:2: error: call to undeclared function
>> 'panic_print_deprecated'; ISO C99 and later do not support implicit
>> function declarations [-Wimplicit-function-declaration]
>> 958 | panic_print_deprecated();
>> | ^
>> 2 errors generated.
>
>
> Oops, panic_print_deprecated() is defined within the #ifdef
> CONFIG_PROC_SYSCTL block, but it's also called from panic_print_set()
Correction:
CONFIG_SYSCTL block - sorry ;(
> and panic_print_get(), which are outside of that block.
>
> So, we need to move the definition out of the block to a common
> scope where all its callers can see it. @Petr wdyt?
>
> Thanks,
> Lance
>
>>
>>
>> vim +/panic_print_deprecated +952 kernel/panic.c
>>
>> 949
>> 950 static int panic_print_set(const char *val, const struct
>> kernel_param *kp)
>> 951 {
>> > 952 panic_print_deprecated();
>> 953 return param_set_ulong(val, kp);
>> 954 }
>> 955
>>
>
next prev parent reply other threads:[~2025-08-20 1:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 7:14 [PATCH 0/3] follow up patches for panic_print's generalization Feng Tang
2025-08-15 7:14 ` [PATCH 1/3] lib/sys_info: handle sys_info_mask==0 case Feng Tang
2025-08-19 8:34 ` Petr Mladek
2025-08-25 1:05 ` Feng Tang
2025-08-15 7:14 ` [PATCH 2/3] panic: refine the document for 'panic_print' Feng Tang
2025-08-19 8:35 ` Petr Mladek
2025-08-15 7:14 ` [PATCH 3/3] panic: add note that 'panic_print' parameter is deprecated Feng Tang
2025-08-19 9:48 ` Petr Mladek
2025-08-19 9:51 ` [PATCH] panic: Clean up message about deprecated 'panic_print' parameter Petr Mladek
2025-08-19 13:58 ` Lance Yang
2025-08-20 1:31 ` kernel test robot
2025-08-20 1:54 ` Lance Yang
2025-08-20 1:56 ` Lance Yang [this message]
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
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=33a897b4-7d9a-4641-9c7a-07c19bb9cb6f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.