From: Juri Lelli <juri.lelli@arm.com>
To: peterz@infradead.org
Cc: luca.abeni@unitn.it, rdunlap@infradead.org, mingo@redhat.com,
henrik@austad.us, raistlin@linux.it, juri.lelli@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@arm.com>
Subject: [PATCH 0/4] SCHED_DEADLINE documentation fixes and improvements
Date: Tue, 12 Aug 2014 16:49:11 +0100 [thread overview]
Message-ID: <1407858555-14371-1-git-send-email-juri.lelli@arm.com> (raw)
Hello everyone,
This small patchset fixes and improves SCHED_DEADLINE documentation.
Patch 1/4 fixes and clarifies terminology; patch 2/4 aligns Section 4 to
the current interface; patch 3/4 improves and clarifies what admission
control means on UP an SMP systems; patch 4/4 introduces an appendix about
testing.
Best Regards,
- Juri
Juri Lelli (2):
Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro
Documentation/scheduler/sched-deadline.txt: add tests suite appendix
Luca Abeni (2):
Documentation/scheduler/sched-deadline.txt: fix terminology and
improve clarity
Documentation/scheduler/sched-deadline.txt: improve and clarify AC
bits
Documentation/scheduler/sched-deadline.txt | 200 ++++++++++++++++++++++------
1 file changed, 156 insertions(+), 44 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-08-12 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 15:49 Juri Lelli [this message]
2014-08-12 15:49 ` [PATCH 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity Juri Lelli
2014-08-12 17:45 ` Randy Dunlap
2014-08-13 9:03 ` Juri Lelli
2014-08-12 15:49 ` [PATCH 2/4] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro Juri Lelli
2014-08-12 15:49 ` [PATCH 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits Juri Lelli
2014-08-12 18:11 ` Randy Dunlap
2014-08-12 20:17 ` Peter Zijlstra
2014-08-12 21:22 ` luca abeni
2014-08-13 9:05 ` Juri Lelli
2014-08-12 15:49 ` [PATCH 4/4] Documentation/scheduler/sched-deadline.txt: add tests suite appendix Juri Lelli
2014-08-12 17:57 ` Randy Dunlap
2014-08-13 9:09 ` Juri Lelli
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=1407858555-14371-1-git-send-email-juri.lelli@arm.com \
--to=juri.lelli@arm.com \
--cc=henrik@austad.us \
--cc=juri.lelli@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=raistlin@linux.it \
--cc=rdunlap@infradead.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).