From: Daniel Wagner <wagi@monom.org>
To: Juri Lelli <juri.lelli@arm.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: "juri.lelli@gmail.com" <juri.lelli@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: Reset bandwith on task when switching from SCHED_DEADLINE away
Date: Tue, 09 Sep 2014 08:22:00 +0200 [thread overview]
Message-ID: <540E9C88.9010200@monom.org> (raw)
In-Reply-To: <540DC7B2.6000000@arm.com>
Hi Juri,
On 09/08/2014 05:13 PM, Juri Lelli wrote:
> thanks a lot for your patch. I'd actually have a slightly different fix
> for the same problem. I'm actually baking a small patchset that I should
> be able to release in the next few days. I'd say we could wait for that
> to happen and then discuss which approach is better, ok?
Sure, no problem. Probably I didn't fix all corner cases anyway.
cheers,
daniel
prev parent reply other threads:[~2014-09-09 6:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 12:29 [PATCH] sched: Reset bandwith on task when switching from SCHED_DEADLINE away Daniel Wagner
2014-09-08 15:13 ` Juri Lelli
2014-09-09 6:22 ` Daniel Wagner [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=540E9C88.9010200@monom.org \
--to=wagi@monom.org \
--cc=juri.lelli@arm.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@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