From: jakub.kicinski at netronome.com (Jakub Kicinski)
Subject: [PATCH v5 bpf-next 0/7] bpftool: support loading flow dissector
Date: Fri, 9 Nov 2018 12:15:11 -0800 [thread overview]
Message-ID: <20181109121511.254dfd59@cakuba.netronome.com> (raw)
In-Reply-To: <20181109162146.78019-1-sdf@google.com>
On Fri, 9 Nov 2018 08:21:39 -0800, Stanislav Fomichev wrote:
> v5 changes:
> * FILE -> PATH for load/loadall (can be either file or directory now)
> * simpler implementation for __bpf_program__pin_name
> * removed p_err for REQ_ARGS checks
> * parse_atach_detach_args -> parse_attach_detach_args
> * for -> while in bpf_object__pin_{programs,maps} recovery
Thanks! Patch 3 needs attention from maintainers but the rest LGTM!
WARNING: multiple messages have this Message-ID (diff)
From: jakub.kicinski@netronome.com (Jakub Kicinski)
Subject: [PATCH v5 bpf-next 0/7] bpftool: support loading flow dissector
Date: Fri, 9 Nov 2018 12:15:11 -0800 [thread overview]
Message-ID: <20181109121511.254dfd59@cakuba.netronome.com> (raw)
Message-ID: <20181109201511.cqa5yDjtS-ScpenBujSK_XrY5n1TkEWU2Scwsi4sFj8@z> (raw)
In-Reply-To: <20181109162146.78019-1-sdf@google.com>
On Fri, 9 Nov 2018 08:21:39 -0800, Stanislav Fomichev wrote:
> v5 changes:
> * FILE -> PATH for load/loadall (can be either file or directory now)
> * simpler implementation for __bpf_program__pin_name
> * removed p_err for REQ_ARGS checks
> * parse_atach_detach_args -> parse_attach_detach_args
> * for -> while in bpf_object__pin_{programs,maps} recovery
Thanks! Patch 3 needs attention from maintainers but the rest LGTM!
next prev parent reply other threads:[~2018-11-09 20:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 16:21 [PATCH v5 bpf-next 0/7] bpftool: support loading flow dissector sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-09 16:21 ` [PATCH v5 bpf-next 1/7] selftests/bpf: rename flow dissector section to flow_dissector sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-09 16:21 ` [PATCH v5 bpf-next 2/7] libbpf: cleanup after partial failure in bpf_object__pin sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-12 21:53 ` kafai
2018-11-12 21:53 ` Martin Lau
2018-11-12 22:10 ` sdf
2018-11-12 22:10 ` Stanislav Fomichev
2018-11-12 23:10 ` kafai
2018-11-12 23:10 ` Martin Lau
2018-11-12 23:29 ` sdf
2018-11-12 23:29 ` Stanislav Fomichev
2018-11-12 23:41 ` kafai
2018-11-12 23:41 ` Martin Lau
2018-11-09 16:21 ` [PATCH v5 bpf-next 3/7] libbpf: bpf_program__pin: add special case for instances.nr == 1 sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-09 16:21 ` [PATCH v5 bpf-next 4/7] libbpf: add internal pin_name sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-09 16:21 ` [PATCH v5 bpf-next 5/7] bpftool: add loadall command sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-09 16:21 ` [PATCH v5 bpf-next 6/7] bpftool: add pinmaps argument to the load/loadall sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-09 16:21 ` [PATCH v5 bpf-next 7/7] bpftool: support loading flow dissector sdf
2018-11-09 16:21 ` Stanislav Fomichev
2018-11-09 17:38 ` [PATCH v5 bpf-next 0/7] " quentin.monnet
2018-11-09 17:38 ` Quentin Monnet
2018-11-09 20:15 ` jakub.kicinski [this message]
2018-11-09 20:15 ` Jakub Kicinski
2018-11-11 0:00 ` alexei.starovoitov
2018-11-11 0:00 ` Alexei Starovoitov
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=20181109121511.254dfd59@cakuba.netronome.com \
--to=linux-kselftest@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