public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Pnina Feder <pnina.feder@mobileye.com>, akpm@linux-foundation.org
Cc: oe-kbuild-all@lists.linux.dev, pmladek@suse.com, bhe@redhat.com,
	linux-kernel@vger.kernel.org, lkp@intel.com, mgorman@suse.de,
	mingo@redhat.com, peterz@infradead.org, pnina.feder@mobileye.com,
	rostedt@goodmis.org, senozhatsky@chromium.org,
	tglx@linutronix.de, vkondra@mobileye.com
Subject: Re: [PATCH v5] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU
Date: Fri, 9 Jan 2026 23:19:34 +0100	[thread overview]
Message-ID: <202601092335.DbBERt3l-lkp@intel.com> (raw)
In-Reply-To: <20260108203612.955769-1-pnina.feder@mobileye.com>

Hi Pnina,

kernel test robot noticed the following build warnings:

[auto build test WARNING on akpm-mm/mm-everything]
[also build test WARNING on linus/master v6.19-rc4 next-20260109]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Pnina-Feder/panic-add-panic_force_cpu-parameter-to-redirect-panic-to-a-specific-CPU/20260109-043725
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20260108203612.955769-1-pnina.feder%40mobileye.com
patch subject: [PATCH v5] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU
config: x86_64-rhel-9.4 (https://download.01.org/0day-ci/archive/20260109/202601092335.DbBERt3l-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260109/202601092335.DbBERt3l-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/202601092335.DbBERt3l-lkp@intel.com/

All warnings (new ones prefixed by >>):

   kernel/panic.c: In function 'do_panic_on_target_cpu':
>> kernel/panic.c:327:17: warning: format '%s' expects argument of type 'char *', but argument 2 has type 'void *' [-Wformat=]
     327 |         panic("%s", info);
         |                ~^   ~~~~
         |                 |   |
         |                 |   void *
         |                 char *
         |                %p


vim +327 kernel/panic.c

   324	
   325	static void do_panic_on_target_cpu(void *info)
   326	{
 > 327		panic("%s", info);
   328	}
   329	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2026-01-09 22:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-01 12:32 [PATCH] panic/kexec: Allow forcing panic execution on a specific CPU Pnina Feder
2026-01-03 18:29 ` Andrew Morton
2026-01-04 10:44 ` kernel test robot
2026-01-04 20:42 ` [PATCH v2] panic: add panic_force_cpu= parameter to redirect panic to " Pnina Feder
2026-01-05 23:34   ` Andrew Morton
2026-01-07 21:27     ` Pnina Feder
2026-01-05  8:18 ` [PATCH v3] " Pnina Feder
2026-01-05 16:50   ` Petr Mladek
2026-01-07 21:27     ` Pnina Feder
2026-01-07 21:56   ` [PATCH v4] " Pnina Feder
2026-01-07 23:10     ` Andrew Morton
2026-01-08 11:49       ` Pnina Feder
2026-01-08  3:11     ` Baoquan He
2026-01-08  7:49       ` Peter Zijlstra
2026-01-08 12:02       ` Pnina Feder
2026-01-08  7:48     ` Peter Zijlstra
2026-01-08 16:36       ` Steven Rostedt
2026-01-08 20:14         ` Pnina Feder
2026-01-08 20:09       ` Pnina Feder
2026-01-12  7:49         ` Peter Zijlstra
2026-01-14 21:57           ` Pnina Feder
2026-01-09  1:18     ` kernel test robot
2026-01-08 20:36   ` [PATCH v5] " Pnina Feder
2026-01-08 21:00     ` Steven Rostedt
2026-01-11 10:05       ` Pnina Feder
2026-01-11 17:13         ` Steven Rostedt
2026-01-09 22:19     ` kernel test robot [this message]
2026-01-09 22:41       ` Andrew Morton
2026-01-11 10:09         ` Pnina Feder

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=202601092335.DbBERt3l-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=pnina.feder@mobileye.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=vkondra@mobileye.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