public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Filippo Santovito <filippo.santovito-06ZeP6ie+xM@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: error in shmctl(2) man page
Date: Thu, 07 Aug 2008 15:34:19 +0200	[thread overview]
Message-ID: <489AF9DB.2040401@gmail.com> (raw)
In-Reply-To: <200807301849.07626.filippo.santovito-06ZeP6ie+xM@public.gmane.org>

Hello Filippo,

Filippo Santovito wrote:
> hi,
> in shmctl(2) man page the ipc_perm struct contains a key field 
> while /usr/include/bits/ipc.h (included in /usr/include/sys/ipc.h) ipc_perm 
> has a __key field.
> which is the error? the h header or the man page?
> thank you for your attention.

Thanks for spotting this.  Of course, it is the man page that is in error.
And in fact the same problem is present for the seq field.  And the same
problems are also present in the semctl(2) and msgctl(2) pages.  All of
this has been fixed for man-pages-3.07.

Thanks for your report!

Cheers

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html

--
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:[~2008-08-07 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 16:49 error in shmctl(2) man page Filippo Santovito
     [not found] ` <200807301849.07626.filippo.santovito-06ZeP6ie+xM@public.gmane.org>
2008-08-07 13:34   ` Michael Kerrisk [this message]

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=489AF9DB.2040401@gmail.com \
    --to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
    --cc=filippo.santovito-06ZeP6ie+xM@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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