From: Daniel Borkmann <daniel@iogearbox•net>
To: Alexei Starovoitov <ast@plumgrid•com>,
"David S. Miller" <davem@davemloft•net>
Cc: Michael Holzheu <holzheu@linux•vnet.ibm.com>,
Fengguang Wu <fengguang.wu@intel•com>,
netdev@vger•kernel.org
Subject: Re: [PATCH net-next] test_bpf: fix sparse warnings
Date: Thu, 14 May 2015 20:17:19 +0200 [thread overview]
Message-ID: <5554E6AF.1050103@iogearbox.net> (raw)
In-Reply-To: <5554D8E4.50500@plumgrid.com>
On 05/14/2015 07:18 PM, Alexei Starovoitov wrote:
...
> 0xffff0000ffffffffLL is unsigned. GCC does the right thing. Here
> we're just shutting up sparse.
Yep, that's clear; to not get any more reminders from Fengguang. ;)
> I actually most of the time use LL as well since it's one character
> shorter.
Ok, I see.
next prev parent reply other threads:[~2015-05-14 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 3:40 [PATCH net-next] test_bpf: fix sparse warnings Alexei Starovoitov
2015-05-14 16:10 ` Daniel Borkmann
2015-05-14 17:18 ` Alexei Starovoitov
2015-05-14 18:17 ` Daniel Borkmann [this message]
2015-05-15 2:47 ` David Miller
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=5554E6AF.1050103@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=ast@plumgrid$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=fengguang.wu@intel$(echo .)com \
--cc=holzheu@linux$(echo .)vnet.ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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