The Linux Kernel Mailing List
 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, pnina.feder@mobileye.com, rostedt@goodmis.org,
	senozhatsky@chromium.org, tglx@linutronix.de,
	vkondra@mobileye.com
Subject: Re: [PATCH v8] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU
Date: Fri, 23 Jan 2026 09:08:52 +0800	[thread overview]
Message-ID: <202601230908.0vB3SoHM-lkp@intel.com> (raw)
In-Reply-To: <20260122102457.1154599-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-rc6 next-20260122]
[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/20260122-182657
base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link:    https://lore.kernel.org/r/20260122102457.1154599-1-pnina.feder%40mobileye.com
patch subject: [PATCH v8] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU
config: openrisc-allnoconfig (https://download.01.org/0day-ci/archive/20260123/202601230908.0vB3SoHM-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260123/202601230908.0vB3SoHM-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/202601230908.0vB3SoHM-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/panic.c:79:14: warning: 'panic_force_buf' defined but not used [-Wunused-variable]
      79 | static char *panic_force_buf;
         |              ^~~~~~~~~~~~~~~


vim +/panic_force_buf +79 kernel/panic.c

    77	
    78	static int panic_force_cpu = -1;
  > 79	static char *panic_force_buf;
    80	

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

  reply	other threads:[~2026-01-23  1:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 10:24 [PATCH v8] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU Pnina Feder
2026-01-23  1:08 ` kernel test robot [this message]
2026-01-23  2:11 ` kernel test robot
2026-01-24  1:14 ` Andrew Morton
2026-01-25 19:11   ` Pnina Feder
2026-01-26 12:26 ` [PATCH] panic: fix unused variable warning when SMP or CRASH_DUMP disabled Pnina Feder
2026-01-29 16:21 ` [PATCH v8] panic: add panic_force_cpu= parameter to redirect panic to a specific CPU 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=202601230908.0vB3SoHM-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=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