public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
	linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: [PATCH 10/23] pthread_rwlockattr_setkind_np.3: SYNOPSIS: Use 'restrict' in prototypes
Date: Mon,  8 Mar 2021 19:53:19 +0100	[thread overview]
Message-ID: <20210308185331.242176-11-alx.manpages@gmail.com> (raw)
In-Reply-To: <20210308185331.242176-1-alx.manpages@gmail.com>

glibc uses 'restrict' in pthread_rwlockattr_getkind_np().
Let's use it here too.

.../glibc$ grep_glibc_prototype pthread_rwlockattr_getkind_np
sysdeps/htl/pthread.h:633:
extern int pthread_rwlockattr_getkind_np (const pthread_rwlockattr_t *
					  __restrict __attr,
					  int *__restrict __pref)
     __THROW __nonnull ((1, 2));
sysdeps/nptl/pthread.h:983:
extern int pthread_rwlockattr_getkind_np (const pthread_rwlockattr_t *
					  __restrict __attr,
					  int *__restrict __pref)
     __THROW __nonnull ((1, 2));
.../glibc$

Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man3/pthread_rwlockattr_setkind_np.3 | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/man3/pthread_rwlockattr_setkind_np.3 b/man3/pthread_rwlockattr_setkind_np.3
index eb2dc19bf..7ade3ba7d 100644
--- a/man3/pthread_rwlockattr_setkind_np.3
+++ b/man3/pthread_rwlockattr_setkind_np.3
@@ -31,9 +31,10 @@ the read-write lock kind of the thread read-write lock attribute object
 .B #include <pthread.h>
 .PP
 .BI "int pthread_rwlockattr_setkind_np(pthread_rwlockattr_t *" attr ,
-.BI "                                   int " pref );
-.BI "int pthread_rwlockattr_getkind_np(const pthread_rwlockattr_t *" attr ,
-.BI "                                   int *" pref );
+.BI "                             int " pref );
+.BI "int pthread_rwlockattr_getkind_np("
+.BI "                             const pthread_rwlockattr_t *restrict " attr ,
+.BI "                             int *restrict " pref );
 .PP
 Compile and link with \fI\-pthread\fP.
 .PP
-- 
2.30.1


  parent reply	other threads:[~2021-03-08 18:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 18:53 [PATCH 00/23] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 4) Alejandro Colomar
2021-03-08 18:53 ` [PATCH 01/23] pthread_attr_setschedpolicy.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-08 18:53 ` [PATCH 02/23] pthread_attr_setscope.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 03/23] pthread_attr_setstackaddr.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 04/23] pthread_attr_setstacksize.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 05/23] pthread_attr_setstack.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 06/23] pthread_create.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 07/23] pthread_getattr_default_np.3: SYNOPSIS: Add missing 'const' Alejandro Colomar
2021-03-08 18:53 ` [PATCH 08/23] pthread_mutexattr_getpshared.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-08 18:53 ` [PATCH 09/23] pthread_mutexattr_setrobust.3: SYNOPSIS: Remove incorrect 'const' Alejandro Colomar
2021-03-08 18:53 ` Alejandro Colomar [this message]
2021-03-08 18:53 ` [PATCH 11/23] pthread_setschedparam.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-08 18:53 ` [PATCH 12/23] putgrent.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 13/23] putpwent.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 14/23] puts.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 15/23] qecvt.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 16/23] random_r.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 17/23] rcmd.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 18/23] readdir_r.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 19/23] realpath.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 20/23] regex.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 21/23] rexec.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 22/23] scandir.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 23/23] " Alejandro Colomar

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=20210308185331.242176-11-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).