From: kbuild test robot <lkp@intel.com>
To: Andrei Vagin <avagin@gmail.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: [net-next:master 518/519] drivers/net/virtio_net.c:1910:3: error: implicit declaration of function '__netif_set_xps_queue'; did you mean 'netif_set_xps_queue'?
Date: Fri, 10 Aug 2018 07:34:18 +0800 [thread overview]
Message-ID: <201808100716.9Q9waRUq%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 36d2f761b5aa688567b6aebdc6d68e73682275d4
commit: 4d99f6602cb552fb58db0c3b1d935bb6fa017f24 [518/519] net: allow to call netif_reset_xps_queues() under cpus_read_lock
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 4d99f6602cb552fb58db0c3b1d935bb6fa017f24
# save the attached .config to linux build tree
GCC_VERSION=7.2.0 make.cross ARCH=sh
All errors (new ones prefixed by >>):
drivers/net/virtio_net.c: In function 'virtnet_set_affinity':
>> drivers/net/virtio_net.c:1910:3: error: implicit declaration of function '__netif_set_xps_queue'; did you mean 'netif_set_xps_queue'? [-Werror=implicit-function-declaration]
__netif_set_xps_queue(vi->dev, mask, i, false);
^~~~~~~~~~~~~~~~~~~~~
netif_set_xps_queue
cc1: some warnings being treated as errors
vim +1910 drivers/net/virtio_net.c
1888
1889 static void virtnet_set_affinity(struct virtnet_info *vi)
1890 {
1891 int i;
1892 int cpu;
1893
1894 /* In multiqueue mode, when the number of cpu is equal to the number of
1895 * queue pairs, we let the queue pairs to be private to one cpu by
1896 * setting the affinity hint to eliminate the contention.
1897 */
1898 if (vi->curr_queue_pairs == 1 ||
1899 vi->max_queue_pairs != num_online_cpus()) {
1900 virtnet_clean_affinity(vi, -1);
1901 return;
1902 }
1903
1904 i = 0;
1905 for_each_online_cpu(cpu) {
1906 const unsigned long *mask = cpumask_bits(cpumask_of(cpu));
1907
1908 virtqueue_set_affinity(vi->rq[i].vq, cpu);
1909 virtqueue_set_affinity(vi->sq[i].vq, cpu);
> 1910 __netif_set_xps_queue(vi->dev, mask, i, false);
1911 i++;
1912 }
1913
1914 vi->affinity_hint_set = true;
1915 }
1916
---
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: 48753 bytes --]
reply other threads:[~2018-08-10 2:01 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=201808100716.9Q9waRUq%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=avagin@gmail.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.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