From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, kernel-team@cloudflare.com
Subject: Re: [PATCH bpf-next] scripts/bpf: Emit an #error directive known types list needs updating
Date: Wed, 16 Oct 2019 14:31:38 +0200 [thread overview]
Message-ID: <20191016123138.GD21367@pc-63.home> (raw)
In-Reply-To: <20191016085811.11700-1-jakub@cloudflare.com>
On Wed, Oct 16, 2019 at 10:58:11AM +0200, Jakub Sitnicki wrote:
> Make the compiler report a clear error when bpf_helpers_doc.py needs
> updating rather than rely on the fact that Clang fails to compile
> English:
>
> ../../../lib/bpf/bpf_helper_defs.h:2707:1: error: unknown type name 'Unrecognized'
> Unrecognized type 'struct bpf_inet_lookup', please add it to known types!
>
> Signed-off-by: Jakub Sitnicki <jakub@cloudflare.com>
Applied, thanks!
next prev parent reply other threads:[~2019-10-16 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 8:58 [PATCH bpf-next] scripts/bpf: Emit an #error directive known types list needs updating Jakub Sitnicki
2019-10-16 12:31 ` Daniel Borkmann [this message]
2019-10-16 20:29 ` Andrii Nakryiko
2019-10-17 9:50 ` Jakub Sitnicki
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=20191016123138.GD21367@pc-63.home \
--to=daniel@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=jakub@cloudflare.com \
--cc=kernel-team@cloudflare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.