From: Quentin Monnet <quentin.monnet@netronome.com>
To: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next] tools: bpftool: doc, add text about feature-subcommand
Date: Wed, 6 Feb 2019 09:42:26 +0000 [thread overview]
Message-ID: <f0c5096c-2b76-e85f-7625-37ddbb5bba41@netronome.com> (raw)
In-Reply-To: <20190206014556.3548-1-bhole_prashant_q7@lab.ntt.co.jp>
2019-02-06 10:45 UTC+0900 ~ Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
> This patch adds missing information about feature-subcommand in
> bpftool.rst
>
> Signed-off-by: Prashant Bhole <bhole_prashant_q7@lab.ntt.co.jp>
My bad, thanks a lot for the update!
> ---
> tools/bpf/bpftool/Documentation/bpftool.rst | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/tools/bpf/bpftool/Documentation/bpftool.rst b/tools/bpf/bpftool/Documentation/bpftool.rst
> index 27153bb816ac..0685d5ada3ce 100644
> --- a/tools/bpf/bpftool/Documentation/bpftool.rst
> +++ b/tools/bpf/bpftool/Documentation/bpftool.rst
> @@ -16,7 +16,7 @@ SYNOPSIS
>
> **bpftool** **version**
>
> - *OBJECT* := { **map** | **program** | **cgroup** | **perf** | **net** }
> + *OBJECT* := { **map** | **program** | **cgroup** | **perf** | **net** | **feature** }
>
> *OPTIONS* := { { **-V** | **--version** } | { **-h** | **--help** }
> | { **-j** | **--json** } [{ **-p** | **--pretty** }] }
> @@ -34,6 +34,8 @@ SYNOPSIS
>
> *NET-COMMANDS* := { **show** | **list** | **help** }
>
> + *FEATURE-COMMANDS* := { **probe** | **help** }
Could you please fix this line to use a tab instead of spaces for
indent, as for the rest of the file?
> +
> DESCRIPTION
> ===========
> *bpftool* allows for inspection and simple modification of BPF objects
>
prev parent reply other threads:[~2019-02-06 9:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 1:45 [PATCH bpf-next] tools: bpftool: doc, add text about feature-subcommand Prashant Bhole
2019-02-06 6:26 ` Y Song
2019-02-06 9:42 ` Quentin Monnet [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=f0c5096c-2b76-e85f-7625-37ddbb5bba41@netronome.com \
--to=quentin.monnet@netronome.com \
--cc=ast@kernel.org \
--cc=bhole_prashant_q7@lab.ntt.co.jp \
--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