linux-kernel - Re: [PATCH 1/1] scheduler: minor improvement to pick_next_highest_task

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Mar 2012 08:50:13 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	"Michael J. Wang" <mjwang@...adcom.com>,
	Yong Zhang <yong.zhang0@...il.com>,
	"mingo@...e.hu" <mingo@...e.hu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"rostedt@...dmis.org" <rostedt@...dmis.org>
Subject: Re: [PATCH 1/1] scheduler: minor improvement to
 pick_next_highest_task_rt in linux-3.3


* Peter Zijlstra <peterz@...radead.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/