From: Helge Deller <deller@gmx.de>
To: kernel test robot <lkp@intel.com>, Sven Schnelle <svens@stackframe.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: arch/parisc/kernel/toc.c:61:32: warning: no previous prototype for 'toc_intr'
Date: Mon, 17 Jan 2022 08:19:59 +0100 [thread overview]
Message-ID: <74ac7cb1-0c04-8eca-679e-5c58cc7c8d3d@gmx.de> (raw)
In-Reply-To: <202201171401.TSfnAVql-lkp@intel.com>
On 1/17/22 07:57, kernel test robot wrote:
> Hi Sven,
>
> FYI, the error/warning still remains.
I'll fix this.
Helge
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 35ce8ae9ae2e471f92759f9d6880eab42cc1c3b6
> commit: bc294838cc3443a2fbec58f8936ad4bd0a0b3055 parisc: add support for TOC (transfer of control)
> date: 3 months ago
> config: parisc-randconfig-r022-20220116 (https://download.01.org/0day-ci/archive/20220117/202201171401.TSfnAVql-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 11.2.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/torvalds/linux.git/commit/?id=bc294838cc3443a2fbec58f8936ad4bd0a0b3055
> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git fetch --no-tags linus master
> git checkout bc294838cc3443a2fbec58f8936ad4bd0a0b3055
> # save the config file to linux build tree
> mkdir build_dir
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=parisc SHELL=/bin/bash arch/parisc/kernel/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All warnings (new ones prefixed by >>):
>
>>> arch/parisc/kernel/toc.c:61:32: warning: no previous prototype for 'toc_intr' [-Wmissing-prototypes]
> 61 | void notrace __noreturn __cold toc_intr(struct pt_regs *regs)
> | ^~~~~~~~
>
>
> vim +/toc_intr +61 arch/parisc/kernel/toc.c
>
> 60
> > 61 void notrace __noreturn __cold toc_intr(struct pt_regs *regs)
> 62 {
> 63 struct pdc_toc_pim_20 pim_data20;
> 64 struct pdc_toc_pim_11 pim_data11;
> 65
> 66 nmi_enter();
> 67
> 68 if (boot_cpu_data.cpu_type >= pcxu) {
> 69 if (pdc_pim_toc20(&pim_data20))
> 70 panic("Failed to get PIM data");
> 71 toc20_to_pt_regs(regs, &pim_data20);
> 72 } else {
> 73 if (pdc_pim_toc11(&pim_data11))
> 74 panic("Failed to get PIM data");
> 75 toc11_to_pt_regs(regs, &pim_data11);
> 76 }
> 77
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
>
prev parent reply other threads:[~2022-01-17 7:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 6:57 kernel test robot
2022-01-17 7:19 ` Helge Deller [this message]
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=74ac7cb1-0c04-8eca-679e-5c58cc7c8d3d@gmx.de \
--to=deller@gmx.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=svens@stackframe.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
all inboxes | Powered by JetHome®