linux-kernel - Re: Fix quilt merge error in acpi-cpufreq.c

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]

Message-ID: <20090415230425.GA13744@elte.hu>
Date:	Thu, 16 Apr 2009 01:04:25 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	torvalds@...ux-foundation.org, hpa@...or.com, tglx@...utronix.de,
	rusty@...tcorp.com.au, linux-kernel@...r.kernel.org,
	davej@...hat.com
Subject: Re: Fix quilt merge error in acpi-cpufreq.c

* Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Wed, 15 Apr 2009 23:03:53 +0200
> Ingo Molnar <mingo@...e.hu> wrote:
> 
> > what can we do?
> 
> Write better patch titles?

Lets start with a patch title that you wrote:

| commit 6b44003e5ca66a3fffeb5bc90f40ada2c4340896
| Author: Andrew Morton <akpm@...ux-foundation.org>
| Date:   Thu Apr 9 09:50:37 2009 -0600
|
|     work_on_cpu(): rewrite it to create a kernel thread on demand
|
|     Impact: circular locking bugfix

... and to which Rusty added an impact line.

Where is the impact in that title you wrote? How could it have been 
written differently to include the impact? Why didnt you give it a 
better title? How can you expect us to do a better title if you 
yourself dont do titles with impact information?

If the impact cannot be included, can it be included elsewhere in 
the commit perhaps? If it can be included elsewhere in the commit, 
is it allowed to be summarized in a structured way, or must it stay 
mixed into a free-flowing text description?

	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/