From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754242AbcAEUGd (ORCPT ); Tue, 5 Jan 2016 15:06:33 -0500 Received: from gabe.freedesktop.org ([131.252.210.177]:49845 "EHLO gabe.freedesktop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754074AbcAEUG2 (ORCPT ); Tue, 5 Jan 2016 15:06:28 -0500 From: Eric Anholt To: Stephen Rothwell Cc: linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Florian Fainelli , Stephen Warren Subject: Re: Including Raspberry Pi -next trees in linux-next In-Reply-To: <20160104182614.4be3fa06@canb.auug.org.au> References: <87fuyozzax.fsf@eliezer.anholt.net> <20160104182614.4be3fa06@canb.auug.org.au> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Tue, 05 Jan 2016 12:06:15 -0800 Message-ID: <87d1tfrdu0.fsf@eliezer.anholt.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Stephen Rothwell writes: > Hi Eric, > > On Sat, 26 Dec 2015 13:15:50 -0800 Eric Anholt wrote: >> >> I'll be sending pull-requests to Florian soon, but I would like to get >> my trees included in linux-next to get increased testing coverage of >> them against everything else going on for 4.5. I'm expecting to produce >> trees under these branch names for the forseeable future. >>=20 >> Repo: https://github.com/anholt/linux.git >>=20 >> branches: >> drm-vc4-next >> bcm2835-dt-next >> bcm2835-soc-next >> bcm2835-drivers-next >> bcm2385-defconfig-next >> (bcm2835-maintainers-next is a placeholder since we have nothing for it >> this round) > > I have added the first 5 from today. Can you tell me which trees they > will be merged via so I can position them in my list correctly, > please? drm-vc4-next goes through airlied's drm-next. bcm2835-* are intended to go through Florian's stblinux tree, though things didn't go that way this time because I'm still figuring out timelines. Looking through Next/Trees, it looks like stblinux isn't in the list. That seems like something that would be useful, given that Florian's been successfully sending pull requests to arm-soc for at least a couple of releases. (<1445718981-13552-1-git-send-email-f.fainelli@gmail.com>, for example). His branches appear to be defconfig/next, devicetree/next, maintainers/next, and soc/next, all on https://github.com/Broadcom/stblinux.git. > Also, I was wondering how they relate to the bcm2835 tree I currently > have (git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi.git > for-next) currently maintained by Stephen Warren (cc'd). Stephen and Lee have limited time to work on 2835 as it's only been a free-time project for them afaict. I offered to help on the merging process, since it's job related. I don't have kernel.org access any more I think, and it turns out github process is familiar to 2835's potential contributors, so it's working out quite well to host the branches there. They're still chiming in with acks and feedback when time permits, though. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJWjCI3AAoJELXWKTbR/J7oTlwP/jr2lJXZfuthv87vbjzvVBW0 vaxzHBjbRxcqRFM0hFsjQ+gEZtkS27n5rmJHJE5CrWfIKEoSbAeY3XGmbYiZoPhU LEpMircjdZ3+LPptX6wRJi0xb6fvaC1qKJEV5bVOklhMDViO+AWr79z2UdPuMcyK d+WFNbpVkG/P/mIQYGNYlRwwAyZ7fxzmnv+J2e/IY/2Un/416xBypwXN0p1z2REK YTLTPLP1mlgzejUDwwZY270hFSKFDfXvTo8eFl7wK2ZAuRB8y5f8wbzPQAuSlVS2 TkeZB0tS5pFLGJ09sBqAp+Ym91ksF9OIOeLyJzW0dNAQZrBnRTOVpCtUcQyh639S zmeIHtjEAjjellkyt7C6lhIgYviABfDVsegQYbUrEAQ8OziubtbllCN/yFeHSsKY LviBcn75w/N9ekjr8VbyqpyBK+1qZHmbkqVz4lBvrPCiRhGDMNx1p9EssxjQ8V6U U/Vup8WdO70yqBoLNFkSucOWLpJ+bGq5bfesaPYV5K/RFDadRAWCRLtisLJL1Arc bKzc+GOKyPvXs/0rZDtXCckSu7JSKOt8vYZM6bC9saJnmY4tg9Utw1THeTtn7zQV IFxJN5esL7iFO6NaNsuYmXu9JlTtgVwtrI4UBF5FIwIIuBLDSlcpuSgiT0UZ9uZ3 Il04MagWYd+a05io2V7p =bl75 -----END PGP SIGNATURE----- --=-=-=--