public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Juri Lelli <juri.lelli@arm.com>
Cc: Daniel Wagner <daniel.wagner@bmw-carit.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"juri.lelli@gmail.com" <juri.lelli@gmail.com>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"vincent@legout.info" <vincent@legout.info>
Subject: Re: [PATCH 0/4] Fix various bits of AC and PI for SCHED_DEADLINE
Date: Fri, 24 Oct 2014 15:39:19 +0200	[thread overview]
Message-ID: <20141024133919.GA21513@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <544A524A.3090305@arm.com>

On Fri, Oct 24, 2014 at 02:21:14PM +0100, Juri Lelli wrote:
> > 
> 
> Peter, maybe you can add it while applying them?

Already done, thanks!

      reply	other threads:[~2014-10-24 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  9:16 [PATCH 0/4] Fix various bits of AC and PI for SCHED_DEADLINE Juri Lelli
2014-10-24  9:16 ` [PATCH 1/4] sched/deadline: fix bandwidth check/update when migrating tasks between exclusive cpusets Juri Lelli
2014-10-24  9:16 ` [PATCH 2/4] sched/deadline: ensure that updates to exclusive cpusets don't break AC Juri Lelli
2014-10-24  9:16 ` [PATCH 3/4] sched/deadline: don't replenish from a !SCHED_DEADLINE entity Juri Lelli
2014-10-28 11:01   ` [tip:sched/core] sched/deadline: Don' t " tip-bot for Juri Lelli
2014-10-24  9:16 ` [PATCH 4/4] sched/deadline: fix races between rt_mutex_setprio and dl_task_timer Juri Lelli
2014-10-28 11:02   ` [tip:sched/core] sched/deadline: Fix races between rt_mutex_setprio() and dl_task_timer() tip-bot for Juri Lelli
2014-10-24 11:34 ` [PATCH 0/4] Fix various bits of AC and PI for SCHED_DEADLINE Daniel Wagner
2014-10-24 13:21   ` Juri Lelli
2014-10-24 13:39     ` Peter Zijlstra [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=20141024133919.GA21513@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=daniel.wagner@bmw-carit.de \
    --cc=juri.lelli@arm.com \
    --cc=juri.lelli@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=vincent@legout.info \
    /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