Netdev List
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andrei Vagin <avagin@openvz.org>
Cc: kbuild-all@01.org, "David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, Andrei Vagin <avagin@gmail.com>
Subject: Re: [PATCH net-next] net: add an empty __netif_set_xps_queue() stab in the !CONFIG_XPS case
Date: Mon, 13 Aug 2018 01:25:38 +0800	[thread overview]
Message-ID: <201808130158.Cvd3srg1%fengguang.wu@intel.com> (raw)
In-Reply-To: <20180810010428.6096-1-avagin@openvz.org>

[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]

Hi Andrei,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Andrei-Vagin/net-add-an-empty-__netif_set_xps_queue-stab-in-the-CONFIG_XPS-case/20180813-001123
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

All errors (new ones prefixed by >>):

   In file included from include/linux/icmpv6.h:13:0,
                    from include/linux/ipv6.h:86,
                    from include/net/ipv6.h:16,
                    from include/linux/sunrpc/clnt.h:28,
                    from include/linux/nfs_fs.h:32,
                    from init/do_mounts.c:32:
>> include/linux/netdevice.h:3423:19: error: redefinition of '__netif_set_xps_queue'
    static inline int __netif_set_xps_queue(struct net_device *dev,
                      ^~~~~~~~~~~~~~~~~~~~~
   include/linux/netdevice.h:3409:19: note: previous definition of '__netif_set_xps_queue' was here
    static inline int __netif_set_xps_queue(struct net_device *dev,
                      ^~~~~~~~~~~~~~~~~~~~~

vim +/__netif_set_xps_queue +3423 include/linux/netdevice.h

c9fbb2d2 Krzysztof Kozlowski 2018-08-10  3422  
c9fbb2d2 Krzysztof Kozlowski 2018-08-10 @3423  static inline int __netif_set_xps_queue(struct net_device *dev,
c9fbb2d2 Krzysztof Kozlowski 2018-08-10  3424  					const unsigned long *mask,
c9fbb2d2 Krzysztof Kozlowski 2018-08-10  3425  					u16 index, bool is_rxqs_map)
c9fbb2d2 Krzysztof Kozlowski 2018-08-10  3426  {
c9fbb2d2 Krzysztof Kozlowski 2018-08-10  3427  	return 0;
c9fbb2d2 Krzysztof Kozlowski 2018-08-10  3428  }
537c00de Alexander Duyck     2013-01-10  3429  #endif
537c00de Alexander Duyck     2013-01-10  3430  

:::::: The code at line 3423 was first introduced by commit
:::::: c9fbb2d25295a566b97d62e6904741e8e1702d83 net: Provide stub for __netif_set_xps_queue if there is no CONFIG_XPS

:::::: TO: Krzysztof Kozlowski <krzk@kernel.org>
:::::: CC: David S. Miller <davem@davemloft.net>

---
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: 6369 bytes --]

      reply	other threads:[~2018-08-12 20:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10  1:04 [PATCH net-next] net: add an empty __netif_set_xps_queue() stab in the !CONFIG_XPS case Andrei Vagin
2018-08-12 17:25 ` kbuild 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=201808130158.Cvd3srg1%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=avagin@gmail.com \
    --cc=avagin@openvz.org \
    --cc=davem@davemloft.net \
    --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