Hi Stephen Can you please add the drm-intel-fixes branch to your linux-next tree on top of the for-linux-next branch you've already included from my drm-intel repo at git://people.freedesktop.org/~danvet/drm-intel ? I'm asking since I've merged a patch to -fixes late in the 3.10 cycle and despite that I've let it soak for almost two week in my -fixes branch it readily blew up once 3.10 shipped. I think that the added tester populace of linux-next could have prevented this gaffle. The bug report for reference: https://bugzilla.kernel.org/show_bug.cgi?id=60530 Note that atm for-linux-next points at the same commit as drm-intel-fixes (since we're in the merge window), so adding this branch shouldn't add new conflicts. I just want to be ready after -rc1 is tagged, since then I'll push our feature branch for 3.12 onto for-linux-next, which will kick the patches on -fixes out of linux-next. Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
