linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: linux-man@vger.kernel.org
Subject: [PATCH] bpf-helpers.7: Remove duplicated words and add missing articles
Date: Tue, 12 Nov 2019 22:45:51 +0100	[thread overview]
Message-ID: <87bltgdb00.fsf@mid.deneb.enyo.de> (raw)

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


             reply	other threads:[~2019-11-12 21:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 21:45 Florian Weimer [this message]
2019-11-19 11:48 ` [PATCH] bpf-helpers.7: Remove duplicated words and add missing articles Michael Kerrisk (man-pages)
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=87bltgdb00.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=linux-man@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;
as well as URLs for NNTP newsgroup(s).