From: Peter Zijlstra <peterz@infradead.org>
To: "Michael J. Wang" <mjwang@broadcom.com>
Cc: Yong Zhang <yong.zhang0@gmail.com>,
"mingo@elte.hu" <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: RE: [PATCH 1/1] scheduler: minor improvement to pick_next_highest_task_rt in linux-3.3
Date: Wed, 21 Mar 2012 20:35:52 +0100 [thread overview]
Message-ID: <1332358552.18960.501.camel@twins> (raw)
In-Reply-To: <2EF88150C0EF2C43A218742ED384C1BC0FC85433@IRVEXCHMB08.corp.ad.broadcom.com>
On Wed, 2012-03-21 at 18:33 +0000, Michael J. Wang wrote:
>
> OK. Thanks. I was afraid the details were too verbose when the fix
> was obvious to the experts. Anyways, I now know the format you
> are expecting, so I will do better next time.
Since you took the trouble to write it, I thought it worth the trouble
to include.
Very often Changelogs are way too spartan (my own included), I can't
recall the amount of times I've kicked myself for leaving out some - at
the time - obvious details.
So I prefer people to go overboard a bit and err on the side of too much
information :-)
next prev parent reply other threads:[~2012-03-21 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 22:26 [PATCH 1/1] scheduler: minor improvement to pick_next_highest_task_rt in linux-3.3 Michael J. Wang
2012-03-20 13:59 ` Steven Rostedt
2012-03-21 1:40 ` Yong Zhang
2012-03-21 1:56 ` Michael J. Wang
2012-03-21 2:12 ` Yong Zhang
2012-03-21 7:49 ` Michael J. Wang
2012-03-21 9:06 ` Peter Zijlstra
2012-03-21 18:33 ` Michael J. Wang
2012-03-21 19:35 ` Peter Zijlstra [this message]
2012-03-22 7:50 ` Ingo Molnar
2012-03-27 15:35 ` [tip:sched/urgent] sched/rt: Improve pick_next_highest_task_rt() tip-bot for Michael J Wang
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=1332358552.18960.501.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjwang@broadcom.com \
--cc=rostedt@goodmis.org \
--cc=yong.zhang0@gmail.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.