Hello Inki, On 12/04/2015 06:00 AM, Inki Dae wrote: > Hi Javier, > > 2015년 12월 03일 22:55에 Javier Martinez Canillas 이(가) 쓴 글: >> Hello Inki, >> >> I found that v2 of this patch is alredy in your exynos-drm for-next branch so >> so I had to revert it in linux-next to apply this one to test. You shouldn't >> push patches that were still not reviewed (specially the ones that weren't >> tested like this one) to your branch that gets pulled by -next. The idea of >> -next is to have some test coverage but it should be as stable as possible. > > exynos-drm/for-next branch is not really for-next branch. This branch is used Well, it is a for-next branch because is pulled by -next. It is listed in: http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Next/Trees drm-exynos git git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git#exynos-drm/for-next > only for integration test. As you know, there are many exynos maintainers > and they have their own repository. So we would need to test the integration. Integration testing is of course very needed and linux-next is for that but what should be tested are the patches that are targeted to mainline. > For this, exynos-drm/for-next is merged to linux-next not Dave's tree. > Only exynos-drm-next branch will be merged to Dave's tree so only reviewed and > tested patches will be merged to exynos-drm-next. > In that case, exynos-drm-next is what should be pulled by linux-next, no the for-next branch. Linux-next is a simulation of what Torvalds would do next so problems are found earlier, ideally before the patches land into mainline. Best regards, -- Javier Martinez Canillas Open Source Group Samsung Research America -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |