All of lore.kernel.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
Subject: [PATCH] sched_setattr.2: Add note about missing glibc wrappers
Date: Mon, 15 Feb 2021 14:15:12 +0100	[thread overview]
Message-ID: <20210215131522.450666-2-alx.manpages@gmail.com> (raw)

......

.../glibc$ grep_glibc_prototype sched_setattr
.../glibc$ grep_glibc_prototype sched_getattr
.../glibc$

Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man2/sched_setattr.2 | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/man2/sched_setattr.2 b/man2/sched_setattr.2
index ecbdbffc4..c79b74a49 100644
--- a/man2/sched_setattr.2
+++ b/man2/sched_setattr.2
@@ -37,6 +37,9 @@ set and get scheduling policy and attributes
 .BI "                  unsigned int " size ", unsigned int " flags );
 .fi
 .\" FIXME . Add feature test macro requirements
+.PP
+.IR Note :
+There are no glibc wrappers for these system calls; see NOTES.
 .SH DESCRIPTION
 .SS sched_setattr()
 The
@@ -388,6 +391,9 @@ These system calls first appeared in Linux 3.14.
 .SH CONFORMING TO
 These system calls are nonstandard Linux extensions.
 .SH NOTES
+Glibc does not provide wrappers for these system calls; call them using
+.BR syscall (2).
+.PP
 .BR sched_setattr ()
 provides a superset of the functionality of
 .BR sched_setscheduler (2),
-- 
2.30.0


             reply	other threads:[~2021-02-15 13:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 13:15 Alejandro Colomar [this message]
2021-02-15 19:56 ` [PATCH] sched_setattr.2: Add note about missing glibc wrappers 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=20210215131522.450666-2-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --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 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.