linux-kernel - Re: [PATCH 13/23] timekeeping: move sysfs layer/drop API calls

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: <20070131114929.GC1847@elte.hu>
Date:	Wed, 31 Jan 2007 12:49:29 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org, johnstul@...ibm.com
Subject: Re: [PATCH 13/23] timekeeping: move sysfs layer/drop API calls


* Daniel Walker <dwalker@...sta.com> wrote:

> This moves the timekeeping sysfs override layer into timekeeping.c and 
> removes the get_next_clocksource and select_clocksource functions, and 
> their component variables, since they are no longer used.

please do these two changes in at least two separate phases. Like for 
the timer.c code movement i'd not do the big code shuffling just now, 
and even if it's done, it should be a /pure/ movement, with all 
preparatory and post changes done in separate patches. That way the 
individual changes are much more reviewable.

	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/