From: Roman Gushchin <guro@fb.com>
To: <netdev@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <kernel-team@fb.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Roman Gushchin <guro@fb.com>,
Quentin Monnet <quentin.monnet@netronome.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>
Subject: [PATCH v2 bpf-next 3/3] bpftool: add bash completion for cgroup tree command
Date: Fri, 6 Jul 2018 11:30:12 -0700 [thread overview]
Message-ID: <20180706183012.6475-3-guro@fb.com> (raw)
In-Reply-To: <20180706183012.6475-1-guro@fb.com>
This commit adds a bash completion to the bpftool cgroup tree
command.
Signed-off-by: Roman Gushchin <guro@fb.com>
Cc: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Quentin Monnet <quentin.monnet@netronome.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>
---
tools/bpf/bpftool/bash-completion/bpftool | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/bpf/bpftool/bash-completion/bpftool b/tools/bpf/bpftool/bash-completion/bpftool
index fffd76f4998b..82681eb9c02a 100644
--- a/tools/bpf/bpftool/bash-completion/bpftool
+++ b/tools/bpf/bpftool/bash-completion/bpftool
@@ -414,6 +414,9 @@ _bpftool()
_filedir
return 0
;;
+ tree)
+ _filedir
+ return 0
attach|detach)
local ATTACH_TYPES='ingress egress sock_create sock_ops \
device bind4 bind6 post_bind4 post_bind6 connect4 \
--
2.14.4
next prev parent reply other threads:[~2018-07-06 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 18:30 [PATCH v2 bpf-next 1/3] bpftool: introduce cgroup tree command Roman Gushchin
2018-07-06 18:30 ` [PATCH v2 bpf-next 2/3] bpftool: document " Roman Gushchin
2018-07-06 18:30 ` Roman Gushchin [this message]
2018-07-06 20:58 ` [PATCH v2 bpf-next 3/3] bpftool: add bash completion for " Jakub Kicinski
2018-07-06 21:29 ` Roman Gushchin
2018-07-06 21:01 ` [PATCH v2 bpf-next 1/3] bpftool: introduce " Jakub Kicinski
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=20180706183012.6475-3-guro@fb.com \
--to=guro@fb.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@netronome.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 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.