* [linux-next:master 6141/6355] kernel/panic.c:70:6: sparse: sparse: symbol 'panic_this_cpu_backtrace_printed' was not declared. Should it be static?
@ 2025-09-04 16:50 kernel test robot
2025-09-05 9:00 ` Petr Mladek
0 siblings, 1 reply; 2+ messages in thread
From: kernel test robot @ 2025-09-04 16:50 UTC (permalink / raw)
To: Sergey Senozhatsky
Cc: oe-kbuild-all, Andrew Morton, Linux Memory Management List, Petr Mladek
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 4ac65880ebca1b68495bd8704263b26c050ac010
commit: 28ec7e0d834d81ef8abeb6a6c1376f1fb26f1510 [6141/6355] panic: remove redundant panic-cpu backtrace
config: i386-randconfig-r132-20250904 (https://download.01.org/0day-ci/archive/20250905/202509050048.FMpVvh1u-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250905/202509050048.FMpVvh1u-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/202509050048.FMpVvh1u-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> kernel/panic.c:70:6: sparse: sparse: symbol 'panic_this_cpu_backtrace_printed' was not declared. Should it be static?
vim +/panic_this_cpu_backtrace_printed +70 kernel/panic.c
68
69 bool panic_triggering_all_cpu_backtrace;
> 70 bool panic_this_cpu_backtrace_printed;
71
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [linux-next:master 6141/6355] kernel/panic.c:70:6: sparse: sparse: symbol 'panic_this_cpu_backtrace_printed' was not declared. Should it be static?
2025-09-04 16:50 [linux-next:master 6141/6355] kernel/panic.c:70:6: sparse: sparse: symbol 'panic_this_cpu_backtrace_printed' was not declared. Should it be static? kernel test robot
@ 2025-09-05 9:00 ` Petr Mladek
0 siblings, 0 replies; 2+ messages in thread
From: Petr Mladek @ 2025-09-05 9:00 UTC (permalink / raw)
To: kernel test robot, Andrew Morton
Cc: Sergey Senozhatsky, oe-kbuild-all, Linux Memory Management List
On Fri 2025-09-05 00:50:11, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 4ac65880ebca1b68495bd8704263b26c050ac010
> commit: 28ec7e0d834d81ef8abeb6a6c1376f1fb26f1510 [6141/6355] panic: remove redundant panic-cpu backtrace
> config: i386-randconfig-r132-20250904 (https://download.01.org/0day-ci/archive/20250905/202509050048.FMpVvh1u-lkp@intel.com/config)
> compiler: gcc-13 (Debian 13.3.0-16) 13.3.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250905/202509050048.FMpVvh1u-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/202509050048.FMpVvh1u-lkp@intel.com/
>
> sparse warnings: (new ones prefixed by >>)
> >> kernel/panic.c:70:6: sparse: sparse: symbol 'panic_this_cpu_backtrace_printed' was not declared. Should it be static?
>
> vim +/panic_this_cpu_backtrace_printed +70 kernel/panic.c
>
> 68
> 69 bool panic_triggering_all_cpu_backtrace;
> > 70 bool panic_this_cpu_backtrace_printed;
> 71
I see that Andrew has already fixed this.
Thanks a lot him for doing it.
Best Regards,
Petr
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2025-09-05 9:00 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-09-04 16:50 [linux-next:master 6141/6355] kernel/panic.c:70:6: sparse: sparse: symbol 'panic_this_cpu_backtrace_printed' was not declared. Should it be static? kernel test robot
2025-09-05 9:00 ` Petr Mladek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox