public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hari Bathini <hbathini@linux.ibm.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Sasha Levin <sashal@kernel.org>
Subject: [linux-stable-rc:linux-5.4.y 2166/3542] arch/powerpc/kernel/smp.c:599:6: error: no previous prototype for 'crash_smp_send_stop'
Date: Tue, 10 May 2022 09:25:34 +0800	[thread overview]
Message-ID: <202205100902.Ey56VTam-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
head:   7dae5fe9ddc036e00696eb0f54f4e7cabc04bb81
commit: 2a8870f5cb2ab56fdf17ef219d9389061ca9a774 [2166/3542] powerpc: handle kdump appropriately with crash_kexec_post_notifiers option
config: powerpc-randconfig-r002-20220509 (https://download.01.org/0day-ci/archive/20220510/202205100902.Ey56VTam-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?id=2a8870f5cb2ab56fdf17ef219d9389061ca9a774
        git remote add linux-stable-rc https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
        git fetch --no-tags linux-stable-rc linux-5.4.y
        git checkout 2a8870f5cb2ab56fdf17ef219d9389061ca9a774
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=powerpc SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

Note: the linux-stable-rc/linux-5.4.y HEAD 7dae5fe9ddc036e00696eb0f54f4e7cabc04bb81 builds fine.
      It only hurts bisectability.

All errors (new ones prefixed by >>):

   arch/powerpc/kernel/smp.c:539:6: error: no previous prototype for 'tick_broadcast' [-Werror=missing-prototypes]
     539 | void tick_broadcast(const struct cpumask *mask)
         |      ^~~~~~~~~~~~~~
   arch/powerpc/kernel/smp.c:549:6: error: no previous prototype for 'debugger_ipi_callback' [-Werror=missing-prototypes]
     549 | void debugger_ipi_callback(struct pt_regs *regs)
         |      ^~~~~~~~~~~~~~~~~~~~~
>> arch/powerpc/kernel/smp.c:599:6: error: no previous prototype for 'crash_smp_send_stop' [-Werror=missing-prototypes]
     599 | void crash_smp_send_stop(void)
         |      ^~~~~~~~~~~~~~~~~~~
   cc1: all warnings being treated as errors


vim +/crash_smp_send_stop +599 arch/powerpc/kernel/smp.c

   598	
 > 599	void crash_smp_send_stop(void)
   600	{
   601		static bool stopped = false;
   602	
   603		if (stopped)
   604			return;
   605	
   606		stopped = true;
   607	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp

                 reply	other threads:[~2022-05-10  1:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202205100902.Ey56VTam-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hbathini@linux.ibm.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpe@ellerman.id.au \
    --cc=sashal@kernel.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