public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Henrik Austad <henrik@austad.us>
Cc: Juri Lelli <juri.lelli@arm.com>,
	luca.abeni@unitn.it, rdunlap@infradead.org, mingo@redhat.com,
	raistlin@linux.it, juri.lelli@gmail.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] SCHED_DEADLINE documentation fixes and improvements
Date: Wed, 10 Sep 2014 10:34:58 +0200	[thread overview]
Message-ID: <20140910083458.GQ6758@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140909211739.GA20822@sisyphus.home.austad.us>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

On Tue, Sep 09, 2014 at 11:17:39PM +0200, Henrik Austad wrote:
> On Tue, Sep 09, 2014 at 10:57:11AM +0100, Juri Lelli wrote:
> > Hello everyone,
> 
> Hi Juri,
> 
> Looks good! Didn't spot anything and pleased to see that minimal main() 
> made it into the appendix! :D
> 
> > This is version 4 of a small patchset that fixes and improves SCHED_DEADLINE
> > documentation.
> > 
> > Patch 1/5 fixes and clarifies terminology; patch 2/5 aligns Section 4 to
> > the current interface; patch 3/5 improves and clarifies what admission
> > control means on UP an SMP systems; patch 4/5 introduces an appendix about
> > testing; patch 5/5 introduces an appendix with a minimal main() for
> > application developers.
> > 

> To the whole series,
> 
> Reviewed-by: Henrik Austad <henrik@austad.us>

Thanks guys!

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

      parent reply	other threads:[~2014-09-10  8:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-09  9:57 [PATCH v4 0/5] SCHED_DEADLINE documentation fixes and improvements Juri Lelli
2014-09-09  9:57 ` [PATCH v4 1/5] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity Juri Lelli
2014-09-16 10:56   ` [tip:sched/core] Documentation/scheduler/sched-deadline.txt: Fix " tip-bot for Luca Abeni
2014-09-09  9:57 ` [PATCH v4 2/5] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro Juri Lelli
2014-09-16 10:57   ` [tip:sched/core] " tip-bot for Juri Lelli
2014-09-09  9:57 ` [PATCH v4 3/5] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits Juri Lelli
2014-09-16 10:57   ` [tip:sched/core] Documentation/scheduler/sched-deadline.txt: Improve " tip-bot for Luca Abeni
2014-09-09  9:57 ` [PATCH v4 4/5] Documentation/scheduler/sched-deadline.txt: add tests suite appendix Juri Lelli
2014-09-16 10:57   ` [tip:sched/core] Documentation/scheduler/sched-deadline.txt: Add " tip-bot for Juri Lelli
2014-09-09  9:57 ` [PATCH v4 5/5] Documentation/scheduler/sched-deadline.txt: add minimal main() appendix Juri Lelli
2014-09-16 10:57   ` [tip:sched/core] Documentation/scheduler/sched-deadline.txt: Add " tip-bot for Juri Lelli
2014-09-09 21:17 ` [PATCH v4 0/5] SCHED_DEADLINE documentation fixes and improvements Henrik Austad
2014-09-10  8:03   ` Juri Lelli
2014-09-10  8:34   ` Peter Zijlstra [this message]

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=20140910083458.GQ6758@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=henrik@austad.us \
    --cc=juri.lelli@arm.com \
    --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=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