On Sun, Dec 16, 2012 at 6:54 AM, Matt Fleming <matt.flem...@intel.com> wrote: > > At least we now know the problem wasn't caused by a memory map issue, > just my buggy patch. > > Linus, Peter, how should we proceed from here? Since the commit and its > dependants have been reverted should we punt for now and try again next > merge window?
Hmm. Since we're several days away from the merge window closing, I think I can apply your fixed patch and then undo the revert. But I'll need to feel confident that it works for me too, because I absolutely detest having kernels that I can't use for development myself (which is why I _very_ aggressively revert stuff that I notice myself: if it's a problem reported by some random user, I try to give developers time to fix it if they are responding to the problem report, but if it's a problem that means that I can't use the current -git tree myself, I tend to revert much more aggressively). So I'll test it and see, and hope for the best, Linus -- 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/