From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-man <linux-man@vger.kernel.org>,
Quentin Monnet <quentin.monnet@netronome.com>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH] bpf-helpers.7: Remove duplicated words and add missing articles
Date: Tue, 19 Nov 2019 12:48:30 +0100 [thread overview]
Message-ID: <CAKgNAkitxPz-SuuQP6du2s332x_1tdbcFQEYpw7ZAJ_6sX8sSg@mail.gmail.com> (raw)
In-Reply-To: <87bltgdb00.fsf@mid.deneb.enyo.de>
Hi Florian,
This page is autogenerated from text in the kernel source. See
man-pages commit 53666f6c30451cde
[[
Generating the page itself is a two-step process. First, the
documentation is extracted from include/uapi/linux/bpf.h, and converted
to a RST (reStructuredText-formatted) page, with the relevant script
from Linux sources:
$ ./scripts/bpf_helpers_doc.py > /tmp/bpf-helpers.rst
The second step consists in turning the RST document into the final man
page, with rst2man:
$ rst2man /tmp/bpf-helpers.rst > bpf-helpers.7
]]
I've just refreshed this manual page as per the above steps, and the
typos you note below are still present.
You'd need to craft a patch against the kernel source file
include/uapi/linux/bpf.h. Or perhaps Quentin or Daniel (who I think
roughly own this file) might make the changes directly.
Thanks,
Michael
On Tue, 12 Nov 2019 at 22:45, Florian Weimer <fw@deneb.enyo.de> wrote:
>
> Signed-off-by: Florian Weimer <fw@deneb.enyo.de>
> ---
> man7/bpf-helpers.7 | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/man7/bpf-helpers.7 b/man7/bpf-helpers.7
> index 6f07f476e..0ac569c1d 100644
> --- a/man7/bpf-helpers.7
> +++ b/man7/bpf-helpers.7
> @@ -1546,8 +1546,8 @@ Where t_enabled is the time enabled for event and t_running is
> the time running for event since last normalization. The
> enabled and running times are accumulated since the perf event
> open. To achieve scaling factor between two invocations of an
> -eBPF program, users can can use CPU id as the key (which is
> -typical for perf array usage model) to remember the previous
> +eBPF program, users can use the CPU id as the key (which is
> +typical for the perf array usage model) to remember the previous
> value and do the calculation inside the eBPF program.
> .TP
> .B Return
> @@ -1605,7 +1605,7 @@ the return value of the probed function, and to set it to \fIrc\fP\&.
> The first argument is the context \fIregs\fP on which the kprobe
> works.
> .sp
> -This helper works by setting setting the PC (program counter)
> +This helper works by setting the PC (program counter)
> to an override function which is run in place of the original
> probed function. This means the probed function is not run at
> all. The replacement function just returns with the required
> --
> 2.20.1
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2019-11-19 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 21:45 [PATCH] bpf-helpers.7: Remove duplicated words and add missing articles Florian Weimer
2019-11-19 11:48 ` Michael Kerrisk (man-pages) [this message]
2019-11-19 11:55 ` Quentin Monnet
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=CAKgNAkitxPz-SuuQP6du2s332x_1tdbcFQEYpw7ZAJ_6sX8sSg@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=daniel@iogearbox.net \
--cc=fw@deneb.enyo.de \
--cc=linux-man@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 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).