public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@arm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] sched/deadline: don't need to check throttled status when switched to dl
Date: Tue, 17 Mar 2015 09:08:31 +0100	[thread overview]
Message-ID: <20150317080831.GB28235@gmail.com> (raw)
In-Reply-To: <20150317022423.GB3953@kernel>


* Wanpeng Li <wanpeng.li@linux.intel.com> wrote:

> Ping Ingo, ;-)

So the changelog is not very readable to me, it has various spelling 
mistakes that make it hard to read. Seems like Juri acked the patch, 
mind asking him to fix the changelog to be readable?

Thanks,

	Ingo

  reply	other threads:[~2015-03-17  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  7:27 [PATCH RESEND] sched/deadline: don't need to check throttled status when switched to dl Wanpeng Li
2015-03-17  2:24 ` Wanpeng Li
2015-03-17  8:08   ` Ingo Molnar [this message]
2015-03-17  8:59     ` Wanpeng Li
2015-03-17  9:50     ` Juri Lelli
2015-03-17  9:50       ` Wanpeng Li

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=20150317080831.GB28235@gmail.com \
    --to=mingo@kernel.org \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=wanpeng.li@linux.intel.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