From: kernel test robot <lkp@intel.com>
To: Greentime Hu <greentime.hu@sifive.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
aou@eecs.berkeley.edu, palmer@dabbelt.com,
paul.walmsley@sifive.com, guoren@linux.alibaba.com
Cc: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/2] riscv: Support irq_work via self IPIs
Date: Wed, 24 Jun 2020 00:19:47 +0800 [thread overview]
Message-ID: <202006240003.JZTGfOAb%lkp@intel.com> (raw)
In-Reply-To: <3c4a03ac99118bc6648d06f62c2f46b877bc8c72.1592918110.git.greentime.hu@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 1657 bytes --]
Hi Greentime,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.8-rc2 next-20200623]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Greentime-Hu/riscv-Add-context-tracker-support/20200623-213029
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git dd0d718152e4c65b173070d48ea9dfc06894c3e5
config: riscv-allyesconfig (attached as .config)
compiler: riscv64-linux-gcc (GCC) 9.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
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
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/riscv/kernel/smp.c:129:6: warning: no previous prototype for 'arch_irq_work_raise' [-Wmissing-prototypes]
129 | void arch_irq_work_raise(void)
| ^~~~~~~~~~~~~~~~~~~
vim +/arch_irq_work_raise +129 arch/riscv/kernel/smp.c
127
128 #ifdef CONFIG_IRQ_WORK
> 129 void arch_irq_work_raise(void)
130 {
131 send_ipi_single(smp_processor_id(), IPI_IRQ_WORK);
132 }
133 #endif
134
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 65097 bytes --]
next prev parent reply other threads:[~2020-06-23 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 13:28 [PATCH 0/2] riscv: Add context tracker support Greentime Hu
2020-06-23 13:28 ` [PATCH 1/2] riscv: Support irq_work via self IPIs Greentime Hu
2020-06-23 16:19 ` kernel test robot [this message]
2020-06-23 13:28 ` [PATCH 2/2] riscv: Enable context tracking Greentime Hu
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=202006240003.JZTGfOAb%lkp@intel.com \
--to=lkp@intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=greentime.hu@sifive.com \
--cc=guoren@linux.alibaba.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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