HI Daniel,
On Tue, 9 Jul 2013 16:48:43 +0200 Daniel Vetter daniel.vetter@ffwll.ch wrote:
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.
Added from today.
Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.
You will need to ensure that the patches/commits in your tree/series have been: * submitted under GPL v2 (or later) and include the Contributor's Signed-off-by, * posted to the relevant mailing list, * reviewed by you (or another maintainer of your subsystem tree), * successfully unit tested, and * destined for the current or next Linux merge window.
Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.