From: Peter Zijlstra <peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Juri Lelli <juri.lelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Dario Faggioli <raistlin-k2GhghHVRtY@public.gmane.org>,
lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Linux API <linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [SCHED_DEADLINE man pages 0/2] Summary
Date: Tue, 13 May 2014 17:27:19 +0200 [thread overview]
Message-ID: <20140513152719.GF2485@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <53723235.40101-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Tue, May 13, 2014 at 04:54:45PM +0200, Michael Kerrisk (man-pages) wrote:
> Peter, at al.
>
> The follow ups to this mail contain the changes to man-pages for
> the new sched_setattr() and sched_getattr() system calls, as well
> as the changes to the sched(7) man page to document the
> SCHED_DEADLINE policy, all new changes in kernel 3.14.
>
> I used the text you submitted, but _heavily_ edited it, and added
> a _lot_ of further details. Therefore, could you (and Juri, and
> Dario?) please carefully review the text.
>
> The follow-up mails are:
>
> [1/2] The sched_setattr.2 page that documents sched_setattr(2)
> and sched_getattr(2).
>
> [2/2] The revisions to the sched(7) page.
>
> In each case, I've posted the formatted output for easy reading,
> and attached the page source to the message.
I've read (as careful as one still can after seeing too much of this)
both texts and they appear to be good.
Thanks for polishing, they are indeed clearer than what I provided.
next prev parent reply other threads:[~2014-05-13 15:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:54 [SCHED_DEADLINE man pages 0/2] Summary Michael Kerrisk (man-pages)
2014-05-13 14:57 ` [SCHED_DEADLINE man pages 1/2] sched_setattr.2 Michael Kerrisk (man-pages)
2014-05-13 15:00 ` [SCHED_DEADLINE man pages 2/2] sched(7) SCHED_DEADLINE Michael Kerrisk (man-pages)
[not found] ` <537233A9.6040102-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-13 15:52 ` Juri Lelli
[not found] ` <20140513175210.49eed2e34ac06a3c109ce963-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-13 17:54 ` Michael Kerrisk (man-pages)
[not found] ` <53723235.40101-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-13 15:27 ` Peter Zijlstra [this message]
2014-05-13 17:56 ` [SCHED_DEADLINE man pages 0/2] Summary Michael Kerrisk (man-pages)
2014-05-13 15:54 ` Juri Lelli
[not found] ` <20140513175416.765abe5b536257ab72d827bc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-13 18:00 ` 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=20140513152719.GF2485@laptop.programming.kicks-ass.net \
--to=peterz-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=juri.lelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=raistlin-k2GhghHVRtY@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 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 NNTP newsgroup(s).