From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Cc: mtk.manpages@gmail.com
Subject: [PATCH 06/12] Fix reference for scheduling discussion
Date: Thu, 10 Nov 2016 11:59:45 +0100 [thread overview]
Message-ID: <f0bf2261-3e72-7b3e-70bd-009e360249ec@gmail.com> (raw)
In-Reply-To: <404e11c0-9f88-b460-7398-d00585a9bf16@gmail.com>
Some time back, I moved the discussion of scheduling from
sched_setscheduler(2) to a new sched(7) page. Adjust the cross
reference in the taskset(1) page accordingly.
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
---
schedutils/taskset.1 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/schedutils/taskset.1 b/schedutils/taskset.1
index 13ed583..c0c933f 100644
--- a/schedutils/taskset.1
+++ b/schedutils/taskset.1
@@ -123,7 +123,7 @@ A user can retrieve the affinity mask of any process.
.BR sched_setaffinity (2)
.sp
See
-.BR sched_setscheduler (2)
+.BR sched (7)
for a description of the Linux scheduling scheme.
.SH AUTHOR
Written by Robert M. Love.
--
2.5.5
next prev parent reply other threads:[~2016-11-10 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <404e11c0-9f88-b460-7398-d00585a9bf16@gmail.com>
2016-11-10 10:59 ` [PATCH 04/12] Fix page cross references Michael Kerrisk (man-pages)
2016-11-10 10:59 ` [PATCH 05/12] Fix section number in lockf() page xref Michael Kerrisk (man-pages)
2016-11-10 10:59 ` Michael Kerrisk (man-pages) [this message]
2016-11-10 10:59 ` [PATCH 07/12] Fix formatting errors in page cross references Michael Kerrisk (man-pages)
2016-11-10 10:59 ` [PATCH 08/12] Replace reference to sigvec(2) with sigaction(2) Michael Kerrisk (man-pages)
2016-11-10 10:59 ` [PATCH 09/12] SEE ALSO: add cross reference to namespaces(7) 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=f0bf2261-3e72-7b3e-70bd-009e360249ec@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.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