From: Daniel Borkmann <daniel@iogearbox.net>
To: ast@kernel.org, davem@davemloft.net, netdev@vger.kernel.org,
yuzibode@126.com
Subject: Re: [PATCH] net: sample/bpf/tracex3_user.c: erase "ARRAY_SIZE" redefined
Date: Thu, 4 Oct 2018 16:33:43 +0200 [thread overview]
Message-ID: <07d3987a-05e2-104b-b7f1-ba9653a4393c@iogearbox.net> (raw)
In-Reply-To: <20181003140248.zdvydnelwhw7wcb6@yubo-2>
On 10/03/2018 04:02 PM, Bo YU wrote:
> There is a warning when compiling bpf program in sample/bpf
>
> BTW,i get the warning from David's net tree, then i git clone
> bpf tree try to compile bpf program,but it tell me failed to
> do that maybe i was not compile the whole kernel once.
> I don't know this is ok or not.
>
> Signed-off-by: Bo YU <tsu.yubo@gmail.com>
Seeing the same, therefore applied to bpf-next with commit message
fixed up a bit, thanks!
prev parent reply other threads:[~2018-10-04 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 14:02 [PATCH] net: sample/bpf/tracex3_user.c: erase "ARRAY_SIZE" redefined Bo YU
2018-10-04 14:33 ` Daniel Borkmann [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=07d3987a-05e2-104b-b7f1-ba9653a4393c@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yuzibode@126.com \
/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