From: Eric Dumazet <eric.dumazet@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net, kafai@fb.com,
songliubraving@fb.com, netdev@vger.kernel.org, yhs@fb.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] bpf:sample: fix field 'lock' has incomplete type in hbm.h
Date: Thu, 4 Apr 2019 01:29:05 -0700 [thread overview]
Message-ID: <af74fc26-2790-d83b-5320-bd4581e00585@gmail.com> (raw)
In-Reply-To: <20190404081620.zx5rt2j2rjvdcglt@yubo-2>
On 04/04/2019 01:16 AM, Bo YU wrote:
> When compiling sample/bpf:
>
> samples/bpf/hbm.h:12:23: error: field ‘lock’ has incomplete type
> struct bpf_spin_lock lock;
>
> Fixes: 187d0738ff35(bpf: Sample HBM BPF program to limit egress bw)
> Signed-off-by: Bo YU <tsu.yubo@gmail.com>
> ---
This patch makes absolutely no sense.
Please carefully read samples/bpf/README.rst
next prev parent reply other threads:[~2019-04-04 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 8:16 [PATCH] bpf:sample: fix field 'lock' has incomplete type in hbm.h Bo YU
2019-04-04 8:29 ` Eric Dumazet [this message]
2019-04-04 12:24 ` Bo YU
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=af74fc26-2790-d83b-5320-bd4581e00585@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).