From: kbuild test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@01.org, Thomas Gleixner <tglx@linutronix.de>,
Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/6] genirq/affinity: update CPU affinity for CPU hotplug events
Date: Sat, 4 Feb 2017 00:17:29 +0800 [thread overview]
Message-ID: <201702040030.n76DhcEL%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170203143600.32307-4-hch@lst.de>
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Hi Christoph,
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.10-rc6]
[cannot apply to next-20170203]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Christoph-Hellwig/genirq-allow-assigning-affinity-to-present-but-not-online-CPUs/20170203-224056
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 6.2.0
reproduce:
wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=ia64
All errors (new ones prefixed by >>):
kernel/irq/affinity.c: In function 'irq_affinity_offline_irq':
>> kernel/irq/affinity.c:264:2: error: implicit declaration of function 'irq_force_complete_move' [-Werror=implicit-function-declaration]
irq_force_complete_move(desc);
^~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/irq_force_complete_move +264 kernel/irq/affinity.c
258
259 /*
260 * Complete the irq move. This cpu is going down and for
261 * non intr-remapping case, we can't wait till this interrupt
262 * arrives at this cpu before completing the irq move.
263 */
> 264 irq_force_complete_move(desc);
265
266 /*
267 * The interrupt descriptor might have been cleaned up
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 45922 bytes --]
next prev parent reply other threads:[~2017-02-03 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 14:35 spread MSI(-X) vectors to all possible CPUs Christoph Hellwig
2017-02-03 14:35 ` [PATCH 1/6] genirq: allow assigning affinity to present but not online CPUs Christoph Hellwig
2017-02-03 14:35 ` [PATCH 2/6] genirq/affinity: assign vectors to all present CPUs Christoph Hellwig
2017-02-03 14:35 ` [PATCH 3/6] genirq/affinity: update CPU affinity for CPU hotplug events Christoph Hellwig
2017-02-03 16:17 ` kbuild test robot [this message]
2017-02-03 17:13 ` kbuild test robot
2017-02-10 11:13 ` Thomas Gleixner
2017-02-03 14:35 ` [PATCH 4/6] blk-mq: include all present CPUs in the default queue mapping Christoph Hellwig
2017-02-03 14:35 ` [PATCH 5/6] blk-mq: create hctx for each present CPU Christoph Hellwig
2017-02-03 14:36 ` [PATCH 6/6] nvme: allocate queues for all possible CPUs Christoph Hellwig
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=201702040030.n76DhcEL%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbuild-all@01.org \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).