From: kernel test robot <lkp@intel.com>
To: Denis Kirjanov <kda@linux-powerpc.org>, netdev@vger.kernel.org
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
brouer@redhat.com, jgross@suse.com, wei.liu@kernel.org,
paul@xen.org, ilias.apalodimas@linaro.org
Subject: Re: [PATCH net-next v13 2/3] xen networking: add basic XDP support for xen-netfront
Date: Sat, 27 Jun 2020 10:42:00 +0800 [thread overview]
Message-ID: <202006271010.B1CVbhhx%lkp@intel.com> (raw)
In-Reply-To: <1593171639-8136-3-git-send-email-kda@linux-powerpc.org>
[-- Attachment #1: Type: text/plain, Size: 1903 bytes --]
Hi Denis,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/0day-ci/linux/commits/Denis-Kirjanov/xen-networking-add-XDP-support-to-xen-netfront/20200626-194340
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 7bed14551659875e1cd23a7c0266394a29a773b3
config: arm64-randconfig-r021-20200624 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 6e11ed52057ffc39941cb2de6d93cae522db4782)
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
# install arm64 cross compiling tool for clang build
# apt-get install binutils-aarch64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=arm64
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 >>):
>> drivers/net/xen-netfront.c:1426:8: warning: format specifies type 'unsigned short' but the argument has type 'int' [-Wformat]
headroom);
^~~~~~~~
1 warning generated.
vim +1426 drivers/net/xen-netfront.c
1417
1418 static int talk_to_netback_xdp(struct netfront_info *np, int xdp)
1419 {
1420 int err;
1421 int headroom;
1422
1423 headroom = xdp ? XDP_PACKET_HEADROOM : 0;
1424 err = xenbus_printf(XBT_NIL, np->xbdev->nodename,
1425 "xdp-headroom", "%hu",
> 1426 headroom);
1427 if (err)
1428 pr_warn("Error writing xdp-headroom\n");
1429
1430 return err;
1431 }
1432
---
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: 35202 bytes --]
next prev parent reply other threads:[~2020-06-27 2:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 11:40 [PATCH net-next v13 0/3] xen networking: add XDP support to xen-netfront Denis Kirjanov
2020-06-26 11:40 ` [PATCH net-next v13 1/3] xen: netif.h: add a new extra type for XDP Denis Kirjanov
2020-06-26 11:40 ` [PATCH net-next v13 2/3] xen networking: add basic XDP support for xen-netfront Denis Kirjanov
2020-06-26 12:09 ` Jesper Dangaard Brouer
2020-06-29 10:13 ` Denis Kirjanov
2020-06-26 16:05 ` Jakub Kicinski
2020-06-29 10:14 ` Denis Kirjanov
2020-06-27 2:42 ` kernel test robot [this message]
2020-06-26 11:40 ` [PATCH net-next v13 3/3] xen networking: add XDP offset adjustment to xen-netback Denis Kirjanov
2020-06-26 11:59 ` Paul Durrant
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=202006271010.B1CVbhhx%lkp@intel.com \
--to=lkp@intel.com \
--cc=brouer@redhat.com \
--cc=clang-built-linux@googlegroups.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jgross@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=kda@linux-powerpc.org \
--cc=netdev@vger.kernel.org \
--cc=paul@xen.org \
--cc=wei.liu@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;
as well as URLs for NNTP newsgroup(s).