All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Luca Abeni <luca.abeni@unitn.it>
Cc: peterz@infradead.org, henrik@austad.us, juri.lelli@gmail.com,
	raistlin@linux.it, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH 0/8] SCHED_DEADLINE documentation update
Date: Sun, 12 Apr 2015 11:47:18 +0200	[thread overview]
Message-ID: <20150412094718.GA1667@gmail.com> (raw)
In-Reply-To: <1428661195-9609-1-git-send-email-luca.abeni@unitn.it>


* Luca Abeni <luca.abeni@unitn.it> wrote:

> Hi all,
> 
> here is an update for Documentation/scheduler/sched-deadline.txt.
> Respect to the RFC I sent few days ago, I:
> 1) Split the patches in a better way, (so that, for example, Zhiqiang Zhang's
>    authorship is preserved)
> 2) Tried to address all the comments I received on the RFC
> 3) Added another patch, to split Section 3 in various subsections.
>    I think it is more readable in this way. Anyway, this is the last patch,
>    so it can easily be skipped if people do not like it.
> 
> I also split in a separate patch the discussion about the relationship between
> tasks' parameters and SCHED_DEADLINE parameters. This is (I think) the only
> part of the patchset that has not been previously discussed; I decided to
> isolate it in its own patch so that other patches can be applied anyway.

Note that your Signed-off-by lines are missing.

I also noticed the following inconsistency: 'utilization' (and 
variants) is spelled in two variants in the text: 'utilization' and 
'utilisation'.

I'd strongly suggest using 'utilization' et al (american spelling), 
because that's how it's spelled in most of the kernel source.

Thanks,

	Ingo

  parent reply	other threads:[~2015-04-12  9:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 10:19 [PATCH 0/8] SCHED_DEADLINE documentation update Luca Abeni
2015-04-10 10:19 ` [PATCH 1/8] Documentation/scheduler/sched-deadline.txt: correct definition of density as C_i/min{D_i,P_i} Luca Abeni
2015-04-10 10:19 ` [PATCH 2/8] Documentation/scheduler/sched-deadline.txt: fix typos Luca Abeni
2015-04-10 10:19 ` [PATCH 3/8] Documentation/scheduler/sched-deadline.txt: use consistent namings Luca Abeni
2015-04-10 10:19 ` [PATCH 4/8] Documentation/scheduler/sched-deadline.txt: remove _i from sum, max and min Luca Abeni
2015-04-10 10:19 ` [PATCH 5/8] Documentation/scheduler/sched-deadline.txt: Some notes on EDF schedulability Luca Abeni
2015-04-10 10:19 ` [PATCH 6/8] Documentation/scheduler/sched-deadline.txt: add some references Luca Abeni
2015-04-10 10:19 ` [PATCH 7/8] Documentation/scheduler/sched-deadline.txt: relationship between tasks' deadlines and scheduling deadlines Luca Abeni
2015-04-10 10:19 ` [PATCH 8/8] Documentation/scheduler/sched-deadline.txt: Split Section 3 Luca Abeni
2015-04-11 12:50 ` [PATCH 0/8] SCHED_DEADLINE documentation update Henrik Austad
2015-04-12  9:47 ` Ingo Molnar [this message]
2015-04-13 12:39   ` Luca Abeni

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=20150412094718.GA1667@gmail.com \
    --to=mingo@kernel.org \
    --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=peterz@infradead.org \
    --cc=raistlin@linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.