All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	"David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Subject: [PATCH] perf_event_open.2: tfix
Date: Mon, 28 Oct 2013 20:39:57 -0400	[thread overview]
Message-ID: <1383007197-1518-1-git-send-email-taffit@debian.org> (raw)

---
 man2/perf_event_open.2 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index f4cb5bd..9fc774c 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -1289,7 +1289,7 @@ When the mapping is
 the
 .I data_tail
 value should be written by user space to reflect the last read data.
-In this case the kernel will not over-write unread data.
+In this case the kernel will not overwrite unread data.
 .PP
 The following 2^n ring-buffer pages have the layout described below.
 
@@ -2133,7 +2133,7 @@ When
 .B E2BIG
 is returned, the perf_event_attr
 .I size 
-field is over-written by the kernel to be the size of the structure
+field is overwritten by the kernel to be the size of the structure
 it was expecting.
 .TP
 .B EINVAL
-- 
1.8.4.rc3

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-10-29  0:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29  0:39 David Prévot [this message]
     [not found] ` <1383007197-1518-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2013-10-30  1:46   ` [PATCH] perf_event_open.2: tfix Michael Kerrisk (man-pages)

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=1383007197-1518-1-git-send-email-taffit@debian.org \
    --to=taffit-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.