From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Alexei Starovoitov <ast@fb.com>
Cc: Andrii Nakryiko <andriin@fb.com>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
Kernel Team <Kernel-team@fb.com>
Subject: Re: [PATCH v2 bpf-next 2/3] scripts/bpf: teach bpf_helpers_doc.py to dump BPF helper definitions
Date: Sat, 5 Oct 2019 22:33:53 -0700 [thread overview]
Message-ID: <CAEf4BzZsKNx=y2WtA2=bV4SBfvEhogudMjx=nrBVBVEFVbrGUQ@mail.gmail.com> (raw)
In-Reply-To: <c2302e65-90e4-adc1-7e6d-7dc324a133c9@fb.com>
On Sat, Oct 5, 2019 at 9:21 PM Alexei Starovoitov <ast@fb.com> wrote:
>
> On 10/5/19 8:20 PM, Andrii Nakryiko wrote:
> > Enhance scripts/bpf_helpers_doc.py to emit C header with BPF helper
> > definitions (to be included from libbpf's bpf_helpers.h).
> >
> > Signed-off-by: Andrii Nakryiko<andriin@fb.com>
> > ---
> > scripts/bpf_helpers_doc.py | 155 +-
> > tools/lib/bpf/bpf_helper_defs.h | 2677 +++++++++++++++++++++++++++++++
> > 2 files changed, 2831 insertions(+), 1 deletion(-)
> > create mode 100644 tools/lib/bpf/bpf_helper_defs.h
>
> patch 2 adds it. patch 3 deletes it? stress testing git? ;)
oh, wow... I checked cover letter's summary stats, didn't see
bpf_helpers_defs.h there and figured I didn't screw up.. wrong!
next prev parent reply other threads:[~2019-10-06 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 3:20 [PATCH v2 bpf-next 0/3] Auto-generate list of BPF helpers Andrii Nakryiko
2019-10-06 3:20 ` [PATCH v2 bpf-next 1/3] uapi/bpf: fix helper docs Andrii Nakryiko
2019-10-06 3:20 ` [PATCH v2 bpf-next 2/3] scripts/bpf: teach bpf_helpers_doc.py to dump BPF helper definitions Andrii Nakryiko
2019-10-06 4:21 ` Alexei Starovoitov
2019-10-06 5:33 ` Andrii Nakryiko [this message]
2019-10-06 3:20 ` [PATCH v2 bpf-next 3/3] libbpf: auto-generate list of " Andrii Nakryiko
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='CAEf4BzZsKNx=y2WtA2=bV4SBfvEhogudMjx=nrBVBVEFVbrGUQ@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=Kernel-team@fb.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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).