> - fixed AR and UC order in enum severity_level because UC is severer than AR > by definition. Current code is not affected by this wrong order by chance.
AR and AO are both UC errors - that happen also to be recoverable. Are you really sure about this re-order not affecting existing code? You might well be right, but as every one else has pointed out mce_severity() is full of odd subtleties that catch people out. Is the "UC" entry at the end of the severities[] table just a catch-all for things that made it past all the other entries? Does it ever really get used? What was the test case that made you promote UC above AR? This absolutely should not be buried in the middle of your other patch - it needs to be separate with a much more than two lines of commit description. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
