On Tue, Jan 14, 2014 at 08:10:28AM -0800, H. Peter Anvin wrote:
> Quite frankly I would be much happier if we didn't stash so much under
> arch/x86/kernel/cpu ... quite frankly it feels like almost *anything*
> could go under there. The microcode code, for example, could go under
> its own subtree.
Yeah, about the microcode, shouldn't it be under kernel/cpu/? My train
of thought is: because it is cpu-related functionality, it logically
belongs there.
Or do we rather apply the shallow tree logic of
arch/x86/microcode
arch/x86/events
...
?
I have to say, arch/x86/kernel/cpu/ is kinda long and hard to remember
so the shallow structure should be nicer on the eyes and the brain :)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|