From: Ingo Molnar <mingo@kernel.org>
To: Wanpeng Li <wanpeng.li@linux.intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2] sched/deadline: fix rt runtime corrupt when dl refuse a smaller bandwidth
Date: Tue, 17 Mar 2015 09:09:08 +0100 [thread overview]
Message-ID: <20150317080908.GC28235@gmail.com> (raw)
In-Reply-To: <20150317022550.GC3953@kernel>
* Wanpeng Li <wanpeng.li@linux.intel.com> wrote:
> Ping Ingo, ;-)
Same observation as for the other patch: 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
next prev parent reply other threads:[~2015-03-17 8:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 7:28 [PATCH RESEND v2] sched/deadline: fix rt runtime corrupt when dl refuse a smaller bandwidth Wanpeng Li
2015-03-17 2:25 ` Wanpeng Li
2015-03-17 8:09 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-25 4:37 Wanpeng Li
2015-02-26 9:55 ` 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=20150317080908.GC28235@gmail.com \
--to=mingo@kernel.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.