public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Henrik Austad <henrik@austad.us>
Cc: Juri Lelli <juri.lelli@arm.com>,
	peterz@infradead.org, 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 v3 0/4] SCHED_DEADLINE documentation fixes and improvements
Date: Wed, 3 Sep 2014 10:46:09 +0200	[thread overview]
Message-ID: <20140903084609.GA8021@gmail.com> (raw)
In-Reply-To: <20140902215510.GE22581@sisyphus.home.austad.us>


* Henrik Austad <henrik@austad.us> wrote:

> On Thu, Aug 28, 2014 at 11:00:25AM +0100, Juri Lelli wrote:
> > Hello everyone,
> > 
> > This is version 3 of a small patchset that 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.
> 
> For patch 1 & 2, please consider adding a Reviewed-by from me 
> (there's some nitpick, but nothing serious).
> 
> For patch 3 & 4 I have some comments, but again, nothing 
> severe. I'd like a short feedback before adding a reviewed-by 
> though.

I had these queued up, but I'll wait for the next round of 
patches before applying them.

Thanks,

	Ingo

      reply	other threads:[~2014-09-03  8:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 10:00 [PATCH v3 0/4] SCHED_DEADLINE documentation fixes and improvements Juri Lelli
2014-08-28 10:00 ` [PATCH v3 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity Juri Lelli
2014-09-02 21:10   ` Henrik Austad
2014-09-03  6:43     ` Luca Abeni
     [not found]       ` <CAM6o_m19T7OV=4_5rh_m1XSZKQmpKD0TaSSkiOxthNLz7uJ8Gw@mail.gmail.com>
2014-09-03  8:27         ` Luca Abeni
2014-09-04  8:46     ` Juri Lelli
2014-08-28 10:00 ` [PATCH v3 2/4] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro Juri Lelli
2014-09-02 21:14   ` Henrik Austad
2014-09-04  8:57     ` Juri Lelli
2014-08-28 10:00 ` [PATCH v3 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits Juri Lelli
2014-09-02 21:45   ` Henrik Austad
2014-09-03  6:49     ` Luca Abeni
     [not found]       ` <CAM6o_m3VXiJO3ED_Rb-_Kfaw7mFyw_s4W0quQ_hSbpxgA_foLA@mail.gmail.com>
2014-09-03  8:37         ` Luca Abeni
2014-09-03  9:18       ` Juri Lelli
2014-09-04  9:25         ` Juri Lelli
2014-08-28 10:00 ` [PATCH v3 4/4] Documentation/scheduler/sched-deadline.txt: add tests suite appendix Juri Lelli
2014-09-02 21:53   ` Henrik Austad
2014-09-04 10:15     ` Juri Lelli
2014-09-02 21:55 ` [PATCH v3 0/4] SCHED_DEADLINE documentation fixes and improvements Henrik Austad
2014-09-03  8:46   ` Ingo Molnar [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=20140903084609.GA8021@gmail.com \
    --to=mingo@kernel.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=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