From: Quentin Monnet <quentin@isovalent.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
Quentin Monnet <quentin@isovalent.com>
Subject: [PATCH bpf-next 1/3] tools: bpftool: fix formatting in bpftool-link documentation
Date: Fri, 4 Sep 2020 17:14:52 +0100 [thread overview]
Message-ID: <20200904161454.31135-2-quentin@isovalent.com> (raw)
In-Reply-To: <20200904161454.31135-1-quentin@isovalent.com>
Fix a formatting error in the documentation for bpftool-link, so that
the man page can build correctly.
Signed-off-by: Quentin Monnet <quentin@isovalent.com>
---
tools/bpf/bpftool/Documentation/bpftool-link.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/bpf/bpftool/Documentation/bpftool-link.rst b/tools/bpf/bpftool/Documentation/bpftool-link.rst
index 4a52e7a93339..dc7693b5e606 100644
--- a/tools/bpf/bpftool/Documentation/bpftool-link.rst
+++ b/tools/bpf/bpftool/Documentation/bpftool-link.rst
@@ -21,7 +21,7 @@ LINK COMMANDS
| **bpftool** **link { show | list }** [*LINK*]
| **bpftool** **link pin** *LINK* *FILE*
-| **bpftool** **link detach *LINK*
+| **bpftool** **link detach** *LINK*
| **bpftool** **link help**
|
| *LINK* := { **id** *LINK_ID* | **pinned** *FILE* }
--
2.20.1
next prev parent reply other threads:[~2020-09-04 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 16:14 [PATCH bpf-next 0/3] bpf: format fixes for BPF helpers and bpftool documentation Quentin Monnet
2020-09-04 16:14 ` Quentin Monnet [this message]
2020-09-04 16:14 ` [PATCH bpf-next 2/3] bpf: fix formatting in documentation for BPF helpers Quentin Monnet
2020-09-04 16:14 ` [PATCH bpf-next 3/3] tools, bpf: synchronise BPF UAPI header with tools Quentin Monnet
2020-09-04 21:40 ` [PATCH bpf-next 0/3] bpf: format fixes for BPF helpers and bpftool documentation Andrii Nakryiko
2020-09-07 14:48 ` Quentin Monnet
2020-09-08 20:09 ` Andrii Nakryiko
2020-09-07 14:35 ` Daniel Borkmann
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=20200904161454.31135-2-quentin@isovalent.com \
--to=quentin@isovalent.com \
--cc=ast@kernel.org \
--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