linux-kernel - Re: [RFC patch 01/32] TRACE_EVENT: gradual semicolon removal

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] [day] [month] [year] [list]

Date:	Tue, 3 May 2011 15:53:02 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [RFC patch 01/32] TRACE_EVENT: gradual semicolon removal

On Tue, May 03, 2011 at 10:37:37AM -0400, Steven Rostedt wrote:

> BTW, next time don't Cc the world on generic patch sets like this. If
> someone is Cc'd in one of the patch sets and wonders what it is about.

OTOH it's nice for maintainers to be told about stuff like this rather
than having to find out through -next failures if they do some
incremental work in the area.

> a) You did not write your change log well enough

> b) It contains unrelated changes

> c) They could look at lkml.org to find out what this patch set is about.

> (c) is what I usually do when I'm Cc'd in a middle of a patch series.

Though in this case the combination of a and b undermined the
effectiveness of c.
--
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/