linux-man.vger.kernel.org archive mirror
 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 2/2] open.2: ffix
Date: Tue, 15 May 2012 22:07:00 -0400	[thread overview]
Message-ID: <1337134020-10063-1-git-send-email-taffit@debian.org> (raw)
In-Reply-To: <1337127028-4505-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>

Hi Michael,

Another similar one I only noticed on review.

---
 man2/open.2 |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man2/open.2 b/man2/open.2
index 5ea16f6..ad318b1 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -776,7 +776,7 @@ I/Os should never be run concurrently with the
 system call,
 if the memory buffer is a private mapping
 (i.e., any mapping created with the
-.BR mmap(2)
+.BR mmap (2)
 .BR MAP_PRIVATE
 flag;
 this includes memory allocated on the heap and statically allocated buffers).
-- 
1.7.10

--
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

  parent reply	other threads:[~2012-05-16  2:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  0:10 [PATCH] open.2: ffix David Prévot
     [not found] ` <1337127028-4505-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-05-16  2:07   ` David Prévot [this message]
     [not found]     ` <1337134020-10063-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-06-07 15:01       ` [PATCH 2/2] " 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=1337134020-10063-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 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).