On Wed, Mar 29, 2017 at 12:15:07AM +0300, Kirill A. Shutemov wrote:
> On current tip/master?
tip/master from Monday:
commit d3b6ed97fbc63219e262faca86da2fe62885eff2 (refs/remotes/tip/master)
Merge: 399c980bd22b f2a6a7050109
Author: Ingo Molnar <mingo@xxxxxxxxxx>
Date: Mon Mar 27 10:48:30 2017 +0200
Merge branch 'x86/mm'
> I'm not sure that collapsing history in one commit to fix bisectability is
> any better than having broken bisectability.
Of course it is better. How do you tell everyone who bisects in the
future to jump over those commits?
So perhaps not a single commit but at least meld those together which
change pagetable walking like the current example and cause a breakage.
Thanks.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
