public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Michael J. Wang" <mjwang@broadcom.com>,
	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: Thu, 22 Mar 2012 08:50:13 +0100	[thread overview]
Message-ID: <20120322075013.GB31810@gmail.com> (raw)
In-Reply-To: <1332358552.18960.501.camel@twins>


* Peter Zijlstra <peterz@infradead.org> wrote:

> 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 :-)

Yeah. Current trends are: for every 1000 patches sent there's 
maybe one patch that has a tad too much information in its 
changelog - but instead offers good entertainment in the 
changelog so it's still perfectly fine. 990 patches have too 
little information. The remaining 9 are just fine.

Thanks,

	Ingo

  reply	other threads:[~2012-03-22  7:50 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
2012-03-22  7:50               ` Ingo Molnar [this message]
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=20120322075013.GB31810@gmail.com \
    --to=mingo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mjwang@broadcom.com \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox