From: Bo Borgerson <gigabo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] sem_overview.7: Fix typo (semget => shmget)
Date: Mon, 29 Mar 2010 19:01:01 -0700 [thread overview]
Message-ID: <4BB15B5D.7050706@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
Hi,
The sem_overview(7) man page makes reference to "a System V shared
memory segment created using semget(2)". Was this intended to be
"shmget(2)"?
Please see attached patch against current git master.
Thanks,
Bo
[-- Attachment #2: 0001-sem_overview.7-Fix-typo-semget-shmget.patch --]
[-- Type: text/x-diff, Size: 919 bytes --]
>From cc406c10dd443f79e9073f053619a9c475ec97ad Mon Sep 17 00:00:00 2001
From: Bo Borgerson <gigabo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Mon, 29 Mar 2010 18:12:33 -0700
Subject: [PATCH] sem_overview.7: Fix typo (semget => shmget)
In reference to creation of a SysV shared memory segment.
---
man7/sem_overview.7 | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/man7/sem_overview.7 b/man7/sem_overview.7
index ef354fe..fb706d2 100644
--- a/man7/sem_overview.7
+++ b/man7/sem_overview.7
@@ -88,7 +88,7 @@ A thread-shared semaphore is placed in an area of memory shared
between by the threads of a process, for example, a global variable.
A process-shared semaphore must be placed in a shared memory region
(e.g., a System V shared memory segment created using
-.BR semget (2),
+.BR shmget (2),
or a POSIX shared memory object built created using
.BR shm_open (3)).
--
1.6.3.3
next reply other threads:[~2010-03-30 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 2:01 Bo Borgerson [this message]
[not found] ` <4BB15B5D.7050706-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-05-22 6:54 ` [PATCH] sem_overview.7: Fix typo (semget => shmget) Michael Kerrisk
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=4BB15B5D.7050706@gmail.com \
--to=gigabo-re5jqeeqqe8avxtiumwx3w@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.