public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luca Abeni <luca.abeni@unitn.it>
To: Henrik Austad <henrik@austad.us>
Cc: Zhiqiang Zhang <zhangzhiqiang.zhang@huawei.com>,
	juri.lelli@arm.com, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org
Subject: Re: [PATCH] Documentation/scheduler/sched-deadline.txt: correct definition of density as C_i/min{D_i,P_i}
Date: Tue, 07 Apr 2015 11:48:07 +0200	[thread overview]
Message-ID: <5523A7D7.80102@unitn.it> (raw)
In-Reply-To: <20150403214713.70e9614b@luca-1225C>

On 04/03/2015 09:47 PM, Luca Abeni wrote:
> On Fri, 3 Apr 2015 19:57:37 +0200
> Henrik Austad <henrik@austad.us> wrote:
[...]
>> I realise that I've reviewed quite a lot of this, and I have some
>> vague memories of this being discussed earlier, Juri? Luca?
> I remember there was a discussion (and I seem to remember that the
> symbol used for the period was changed at least one time, but I might
> be wrong), but I do not remember the details.
>
> Next week I'll have some time for working on this; I'll search the old
> emails and I'll try to reconstruct the discussion.
Sorry, after searching in my old emails I've not been able to find
references to this particular topic (T_i vs P_i).
Maybe I lost some emails, or maybe I mis-remembered the old discussion...

Anyway, as I said I am fine with changing P_i in T_i if there is a general
agreement.



				Luca

      reply	other threads:[~2015-04-07  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03  8:18 [PATCH] Documentation/scheduler/sched-deadline.txt: correct definition of density as C_i/min{D_i,P_i} Zhiqiang Zhang
2015-04-03 10:52 ` Luca Abeni
2015-04-08  9:31   ` Juri Lelli
2015-04-08 10:34     ` Luca Abeni
2015-04-03 17:57 ` Henrik Austad
2015-04-03 19:47   ` Luca Abeni
2015-04-07  9:48     ` Luca Abeni [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=5523A7D7.80102@unitn.it \
    --to=luca.abeni@unitn.it \
    --cc=henrik@austad.us \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zhangzhiqiang.zhang@huawei.com \
    /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