netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: kbuild test robot <lkp@intel.com>, Jason Wang <jasowang@redhat.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, mst@redhat.com, jbrouer@redhat.com,
	Jesper Dangaard Brouer <brouer@redhat.com>
Subject: Re: [PATCH net-next 2/2] tuntap: XDP transmission
Date: Sun, 31 Dec 2017 19:55:17 -0800	[thread overview]
Message-ID: <1514778917.1967.36.camel@perches.com> (raw)
In-Reply-To: <201801011138.2pk1NgsN%fengguang.wu@intel.com>

On Mon, 2018-01-01 at 11:48 +0800, kbuild test robot wrote:
> Hi Jason,
> 
> I love your patch! Perhaps something to improve:
> 
> [auto build test WARNING on net-next/master]
> 
> url:    https://github.com/0day-ci/linux/commits/Jason-Wang/XDP-transmission-for-tuntap/20180101-105946
> config: i386-randconfig-x072-201800 (attached as .config)
> compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> 
> All warnings (new ones prefixed by >>):
> 
>    drivers//net/tun.c: In function 'tun_xdp_to_ptr':
> > > drivers//net/tun.c:251:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
> 
>      return (void *)((unsigned long)ptr | TUN_XDP_FLAG);
>             ^
>    drivers//net/tun.c: In function 'tun_ptr_to_xdp':
>    drivers//net/tun.c:257:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
>      return (void *)((unsigned long)ptr & ~TUN_XDP_FLAG);
>             ^
> 
> vim +251 drivers//net/tun.c
> 
>    248	
>    249	void *tun_xdp_to_ptr(void *ptr)
>    250	{
>  > 251		return (void *)((unsigned long)ptr | TUN_XDP_FLAG);

Does TUN_XDP_FLAG really need to be 0x1ULL?
Wouldn't 0x1UL suffice?

  reply	other threads:[~2018-01-01  3:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-29 10:00 [PATCH net-next 0/2] XDP transmission for tuntap Jason Wang
2017-12-29 10:00 ` [PATCH net-next 1/2] tun/tap: use ptr_ring instead of skb_array Jason Wang
2017-12-29 10:00 ` [PATCH net-next 2/2] tuntap: XDP transmission Jason Wang
2017-12-29 12:32   ` Jesper Dangaard Brouer
2018-01-02  3:00     ` Jason Wang
2018-01-01  3:48   ` kbuild test robot
2018-01-01  3:55     ` Joe Perches [this message]
2018-01-02  3:32       ` Jason Wang
2018-01-01  4:09   ` kbuild test robot
2018-01-01  8:27   ` kbuild test robot

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=1514778917.1967.36.camel@perches.com \
    --to=joe@perches.com \
    --cc=brouer@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jbrouer@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mst@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).