Clearing it in the cpuinfo is just a cosmetic side effect which doesOh yes, it does. It makes people unaware that their CPUs _should_ be
no harm at all.
supporting PAT. The thing's not called /proc/kernelinfo for a reason.
it's named /proc/cpuinfo
and this unawareness of the until now not utilized PAT feature is the
least of our worries vs. PAT
You misunderstood. Yinghai's patch only changed one of the code sitesAnd this patch (by the author of the code himself) is the first time whereVery interesting analysis. What broke ? This CPU was never in the set
it breaks.
of supported ones at all.
and not the others, which (if I understood right) is the breakage
Adrian was reffering to.
I know exactly what he was referring to. So what's the problem ?
Yinghai missed to add it to the other place and he is hardly to blame
for that. This code is messy and thats not his fault.
And would yelling at people how shuffle in code without (publicly at
least) addressing one of your fellow arch maintainers objections
1) hpa asked a question http://lkml.org/lkml/2008/3/25/118
2) his question was answered http://lkml.org/lkml/2008/3/25/292
3) hpa did not object (no lkml ref, because there is none)
So what's your point ? Throwing factoids into a discussion is
not really helpful.
and Pavel's review comments about code duplication without a single
line of explanation/changelog do?
As I said before. The changelog is useless and Adrians point about
that is completely correct.