From: Luca Abeni <luca.abeni@unitn.it>
To: Ingo Molnar <mingo@kernel.org>
Cc: Juri Lelli <juri.lelli@arm.com>,
peterz@infradead.org, 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
Subject: Re: [PATCH v2 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits
Date: Fri, 22 Aug 2014 22:14:36 +0200 [thread overview]
Message-ID: <20140822221436.56383b80@luca-1225C> (raw)
In-Reply-To: <20140822083110.GB8771@gmail.com>
Hi,
On Fri, 22 Aug 2014 10:31:11 +0200
Ingo Molnar <mingo@kernel.org> wrote:
[...]
> > > > + execution time is guaranteed for non real-time tasks, which
> > > > risk to be
> > > > + starved by real-time tasks.
> > >
> > > The last part doesn't really parse as correct English for me -
> > > maybe also split this overly long sentence into two or three
> > > sentences, to make it easier to understand?
> > Sorry about this; after re-reading the sentence, I agree it looks
> > confusing. What about:
>
> Looks good to me, with a few details:
[...]
Thanks for the suggestions, and sorry about my bad English; I will send
a new patch to Juri in few days.
Thanks,
Luca
next prev parent reply other threads:[~2014-08-22 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 9:01 [PATCH v2 0/4] SCHED_DEADLINE documentation fixes and improvements Juri Lelli
2014-08-21 9:01 ` [PATCH v2 1/4] Documentation/scheduler/sched-deadline.txt: fix terminology and improve clarity Juri Lelli
2014-08-21 9:01 ` [PATCH v2 2/4] Documentation/scheduler/sched-deadline.txt: Rewrite section 4 intro Juri Lelli
2014-08-21 13:46 ` Ingo Molnar
2014-08-26 8:31 ` Juri Lelli
2014-08-21 9:01 ` [PATCH v2 3/4] Documentation/scheduler/sched-deadline.txt: improve and clarify AC bits Juri Lelli
2014-08-21 13:38 ` Ingo Molnar
2014-08-21 14:47 ` Luca Abeni
2014-08-22 8:31 ` Ingo Molnar
2014-08-22 20:14 ` Luca Abeni [this message]
2014-08-21 9:01 ` [PATCH v2 4/4] Documentation/scheduler/sched-deadline.txt: add tests suite appendix 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=20140822221436.56383b80@luca-1225C \
--to=luca.abeni@unitn.it \
--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=mingo@kernel.org \
--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
all inboxes | Powered by JetHome®