diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-10-29 12:47:46 +0200 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2016-10-29 13:43:30 +0200 |
| commit | 47a2bb177e2802f4a4fa41bea3a79f54a99115da (patch) | |
| tree | 8086722bb4ec41718191847c99e547b471268a1a /man7/sched.7 | |
| parent | b237b37c70a48a3419e4bef5d7da1290f98801ad (diff) | |
| download | man-pages-47a2bb177e2802f4a4fa41bea3a79f54a99115da.tar.gz | |
sched.7: srcfix: FIXME tidy-up
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat (limited to 'man7/sched.7')
| -rw-r--r-- | man7/sched.7 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/man7/sched.7 b/man7/sched.7 index 8dcbd588a5..163c8fc2eb 100644 --- a/man7/sched.7 +++ b/man7/sched.7 @@ -280,8 +280,8 @@ structure; see .BR sched_setattr (2). These fields express values in nanoseconds. .\" FIXME It looks as though specifying sched_period as 0 means -.\" "make sched_period the same as sched_deadline". -.\" This needs to be documented. +.\" "make sched_period the same as sched_deadline". +.\" This needs to be documented. If .IR sched_period is specified as 0, then it is made the same as @@ -349,8 +349,8 @@ thread that calls will yield the current job and wait for a new period to begin. .\" .\" FIXME Calling sched_getparam() on a SCHED_DEADLINE thread -.\" fails with EINVAL, but sched_getscheduler() succeeds. -.\" Is that intended? (Why?) +.\" fails with EINVAL, but sched_getscheduler() succeeds. +.\" Is that intended? (Why?) .\" .SS SCHED_OTHER: Default Linux time-sharing scheduling \fBSCHED_OTHER\fP can be used at only static priority 0. |