linux-kernel - Re: + clocksource-driver-initialize-list-value.patch added to -mm tree

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, 05 Apr 2007 08:02:33 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>, johnstul@...ibm.com,
	LKML <linux-kernel@...r.kernel.org>, heiko.carstens@...ibm.com
Subject: Re: + clocksource-driver-initialize-list-value.patch added to -mm
	tree

On Wed, 2007-04-04 at 17:34 -0700, Daniel Walker wrote:
> > The fact that a list is used to string together clocksource structures
> > is an internal detail of the clock subsystem.  It's annoying that there
> > has to be a list head in the clocksource structure, but at least as a
> > clocksource implementer I can ignore it, and if it ever gets changed to
> > something else I can keep ignoring it.  Your change makes it something
> > that gets pointlessly replicated all over the kernel.
> 
> It's already been discussed in the past, but the clocksource structure
> is already very simple.. Adding a list initializer doesn't change
> anything..

And it does not gain anything. 

So what's the gain of this ? Nine useless entries in the changelog.

	tglx


-
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/