All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nikola Forró" <nforro-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [patch] sched.7: Fix swapped descriptions of sched_get_priority_max and sched_get_priority_min
Date: Tue, 04 Aug 2015 12:08:40 +0200	[thread overview]
Message-ID: <1438682920.3375.7.camel@redhat.com> (raw)

---
 man7/sched.7 | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/man7/sched.7 b/man7/sched.7
index ac518b2..743d52b 100644
--- a/man7/sched.7
+++ b/man7/sched.7
@@ -49,10 +49,10 @@ Set the scheduling parameters of a specified
thread.
 Fetch the scheduling parameters of a specified thread.
 .TP
 .BR sched_get_priority_max (2)
-Return the minimum priority available in a specified scheduling
policy.
+Return the maximum priority available in a specified scheduling
policy.
 .TP
 .BR sched_get_priority_min (2)
-Return the maximum priority available in a specified scheduling
policy.
+Return the minimum priority available in a specified scheduling
policy.
 .TP
 .BR sched_rr_get_interval (2)
 Fetch the quantum used for threads that are scheduled under
-- 
2.4.3
--
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

             reply	other threads:[~2015-08-04 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 10:08 Nikola Forró [this message]
     [not found] ` <1438682920.3375.7.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-08-05 19:14   ` [patch] sched.7: Fix swapped descriptions of sched_get_priority_max and sched_get_priority_min Michael Kerrisk (man-pages)
     [not found]     ` <55C26088.9090604-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-08-10 12:32       ` Nikola Forró

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=1438682920.3375.7.camel@redhat.com \
    --to=nforro-h+wxahxf7alqt0dzr+alfa@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.