mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	luca abeni <luca.abeni@santannapisa.it>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Tommaso Cucinotta <tommaso.cucinotta@sssup.it>
Subject: Re: [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period
Date: Mon, 13 Feb 2017 15:35:11 +0000	[thread overview]
Message-ID: <20170213153511.GG3432@e106622-lin> (raw)
In-Reply-To: <20170213095949.48770eb0@gandalf.local.home>

On 13/02/17 09:59, Steven Rostedt wrote:
> On Mon, 13 Feb 2017 12:10:25 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
> 
> 
> > I've interpreted this as:
> > 
> > Reviewed-by: Luca Abeni <luca.abeni@santannapisa.it>
> > 
> > Holler if you disagree.
> 
> You can add mine too. I put in a lot of trace_printk()s and it all
> appears to be exactly as Daniel describes.
> 
> Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> 

I'm a bit late, but I looked at it as well and it looks good.

If you want,

Reviewed-by: Juri Lelli <juri.lelli@arm.com>

Thanks!

- Juri

  reply	other threads:[~2017-02-13 15:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 19:48 [PATCH 0/2] sched/deadline: Fixes for constrained deadline tasks Daniel Bristot de Oliveira
2017-02-10 19:48 ` [PATCH 1/2] sched/deadline: Replenishment timer should fire in the next period Daniel Bristot de Oliveira
2017-02-10 21:47   ` Steven Rostedt
2017-02-11  7:12   ` luca abeni
2017-02-13 11:10     ` Peter Zijlstra
2017-02-13 14:59       ` Steven Rostedt
2017-02-13 15:35         ` Juri Lelli [this message]
2017-02-10 19:48 ` [PATCH 2/2] sched/deadline: Throttle a constrained deadline task activated after the deadline Daniel Bristot de Oliveira
2017-02-11  7:15   ` luca abeni
2017-02-11  8:00     ` Mike Galbraith
2017-02-11 14:35       ` Steven Rostedt
2017-02-13 11:12     ` Peter Zijlstra
2017-02-13 11:12   ` Peter Zijlstra
2017-02-13 13:16     ` Daniel Bristot de Oliveira
2017-02-13 15:33   ` Steven Rostedt
2017-02-13 15:46     ` Daniel Bristot de Oliveira
2017-02-13 16:21       ` Daniel Bristot de Oliveira

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=20170213153511.GG3432@e106622-lin \
    --to=juri.lelli@arm.com \
    --cc=bristot@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@santannapisa.it \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tommaso.cucinotta@sssup.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 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®