Ingo Molnar wrote:
Well, "no functional changes" is not quite the same thing as "no
object code changes".
yeah, true, but the safest way to ensure no functional changes is to get
identical object code. In sched-devel.git i include obj comparisons to
cleanup patches as a self-assurance (and later bughunt helper) to make
sure a cleanup is really just a cleanup.
Of course. "No object code changes" is a stronger statement, however,
not all types of cleanups result in that.
It's highly useful when applied appropriately, though. In particular,
the programmer should know when object code changes are expected.
-hpa
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
