as a maintainer of "linux_logo" which delves heavily (and perhaps
unwisely) into /proc/cpuinfo and its ilk, I would definitely say I would
not be jumping at the opportunity.
Remember as maintainers of userspace apps, we have to keep compatibility,
in this case for me it involves /proc/cpuinfo from all the architectures,
plus kernels going back to the 1.2.13 time-frame.
So changing /proc/cpuinfo yet again does not simplify the code, in fact it
just adds one more incompatible special case.
And since 2.2 and 2.4 kernels will be around for ages to come, it will
make code bigger rather than smaller.
I agree a cleanup, if done properly, would be welcomed. but don't use
"simplification of user-space code" as an argument.. because it's a lie ;)
Vince
who is perhaps bitter because of all the gratuitious "spaces.. no, tabs..
no, underscores" and "bogomips BOGOmips BogoMips BoGoMiPs bobo_mips" type
changes over the years
-- ____________ \ /\ /\ / Vince Weaver Linux 2.4.17-rc1 on a K6-2+, Up 59 days \/__\/__\/ vince@deater.net http://www.deater.net/weave- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/