From: Daniel Borkmann <daniel@iogearbox.net>
To: Martin KaFai Lau <kafai@fb.com>, Quentin Monnet <quentin@isovalent.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/2] tools: bpftool: fix object pinning and bash
Date: Fri, 13 Mar 2020 00:29:26 +0100 [thread overview]
Message-ID: <af195126-9c8c-d6c2-f317-ab829319c8ba@iogearbox.net> (raw)
In-Reply-To: <20200312202512.yuiesbhlrsglziap@kafai-mbp>
On 3/12/20 9:25 PM, Martin KaFai Lau wrote:
> On Thu, Mar 12, 2020 at 06:46:06PM +0000, Quentin Monnet wrote:
>> The first patch of this series improves user experience by allowing to pass
>> all kinds of handles for programs and maps (id, tag, name, pinned path)
>> instead of simply ids when pinning them with "bpftool (prog|map) pin".
>>
>> The second patch improves or fix bash completion, including for object
>> pinning.
>>
>> v2: Restore close() on file descriptor after pinning the object.
> Acked-by: Martin KaFai Lau <kafai@fb.com>
Applied, thanks!
prev parent reply other threads:[~2020-03-12 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 18:46 [PATCH bpf-next v2 0/2] tools: bpftool: fix object pinning and bash Quentin Monnet
2020-03-12 18:46 ` [PATCH bpf-next v2 1/2] tools: bpftool: allow all prog/map handles for pinning objects Quentin Monnet
2020-03-12 18:46 ` [PATCH bpf-next v2 2/2] tools: bpftool: fix minor bash completion mistakes Quentin Monnet
2020-03-12 20:25 ` [PATCH bpf-next v2 0/2] tools: bpftool: fix object pinning and bash Martin KaFai Lau
2020-03-12 23:29 ` 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=af195126-9c8c-d6c2-f317-ab829319c8ba@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=quentin@isovalent.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).