Hi Stephen, On Mon, Apr 3, 2017 at 7:56 AM, Stephen Rothwell <s...@canb.auug.org.au> wrote: > Hi Maxime, > > On Fri, 31 Mar 2017 09:57:29 +0200 Maxime Ripard > <maxime.rip...@free-electrons.com> wrote: >> >> We've switched from my personal git tree for the Allwinner sunxi >> development to a shared tree: >> git://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git >> >> The branch to be included in linux-next will still be called >> sunxi/for-next as it used to be, and it will still go through the >> arm-soc tree to reach Linux. >> >> However, I'll still have the patches for our DRM drivers on my >> personal git repo: >> git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git >> >> Could you add the branch sunxi-drm/for-next to the list of branches >> you merge? > > OK, just so we are on the same page: > > Currently I have: > > git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git branch > sunxi/for-next > > merged after the drm tree. > > You want: > > git://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux.git branch > sunxi/for-next > > merged after the arm-soc tree and > > git://git.kernel.org/pub/scm/linux/kernel/git/mripard/linux.git branch > sunxi-drm/for-next > > merged after the drm tree? > > (I merge trees *after* the tree that is their upstream.) > > Do you want to be the only contact for both trees?
Please add me as a contact for sunxi/for-next. Thanks ChenYu > -- > Cheers, > Stephen Rothwell