On 06/24/2012 01:39 PM, H. Peter Anvin wrote:
It isn't about finger-pointing, it is about a failure of process; we had a process that would have caught this problem and the process failed. There are certainly blame enough to go around, but I think one of the things here is that lack of response isn't necessary an ACK - it may actually be that the patch looked at first glance like it had no impact on our area (incorrectly as it turned out.)
Let me be clear: I'm not blaming you, or anyone else, personally. Like many other failures, there were a number of steps in the chain here, one of them being not checking this in the script from the beginning, and that one is mine.
-hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- 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
|