From: kernel test robot <lkp@intel.com>
To: Qi Zheng <zhengqi.arch@bytedance.com>,
will@kernel.org, arnd@arndb.de, catalin.marinas@arm.com,
mark.rutland@arm.com
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Qi Zheng <zhengqi.arch@bytedance.com>
Subject: Re: [PATCH v2] arm64: run softirqs on the per-CPU IRQ stack
Date: Sun, 7 Aug 2022 21:47:18 +0800 [thread overview]
Message-ID: <202208072123.sWU13g72-lkp@intel.com> (raw)
In-Reply-To: <20220802065325.39740-1-zhengqi.arch@bytedance.com>
Hi Qi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on soc/for-next]
[also build test WARNING on v5.19]
[cannot apply to arm64/for-next/core linus/master next-20220805]
[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/Qi-Zheng/arm64-run-softirqs-on-the-per-CPU-IRQ-stack/20220802-145547
base: https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git for-next
config: arm64-randconfig-r024-20220801 (https://download.01.org/0day-ci/archive/20220807/202208072123.sWU13g72-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.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://github.com/intel-lab-lkp/linux/commit/34ac9375ce5e75127084159f724fcb2208c022a3
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Qi-Zheng/arm64-run-softirqs-on-the-per-CPU-IRQ-stack/20220802-145547
git checkout 34ac9375ce5e75127084159f724fcb2208c022a3
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm64 SHELL=/bin/bash arch/arm64/kernel/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/arm64/kernel/irq.c:81:6: warning: no previous prototype for 'do_softirq_own_stack' [-Wmissing-prototypes]
81 | void do_softirq_own_stack(void)
| ^~~~~~~~~~~~~~~~~~~~
arch/arm64/kernel/irq.c:120:13: warning: no previous prototype for 'init_IRQ' [-Wmissing-prototypes]
120 | void __init init_IRQ(void)
| ^~~~~~~~
vim +/do_softirq_own_stack +81 arch/arm64/kernel/irq.c
80
> 81 void do_softirq_own_stack(void)
82 {
83 call_on_irq_stack(NULL, ____do_softirq);
84 }
85 #endif
86
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-08-07 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 6:53 [PATCH v2] arm64: run softirqs on the per-CPU IRQ stack Qi Zheng
2022-08-05 7:10 ` Qi Zheng
2022-08-05 7:50 ` Arnd Bergmann
2022-08-05 7:54 ` Qi Zheng
2022-08-07 13:47 ` kernel test robot
2022-08-07 13:47 ` kernel test robot [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=202208072123.sWU13g72-lkp@intel.com \
--to=lkp@intel.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=zhengqi.arch@bytedance.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