From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753176AbcAEV1M (ORCPT ); Tue, 5 Jan 2016 16:27:12 -0500 Received: from mout.kundenserver.de ([212.227.17.24]:58345 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752052AbcAEV1I (ORCPT ); Tue, 5 Jan 2016 16:27:08 -0500 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Stephen Warren , Eric Anholt , Stephen Rothwell , Florian Fainelli , linux-rpi-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: Including Raspberry Pi -next trees in linux-next Date: Tue, 05 Jan 2016 22:26:33 +0100 Message-ID: <3082544.lZk2r7IkWv@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <568C2619.20705@wwwdotorg.org> References: <87fuyozzax.fsf@eliezer.anholt.net> <87d1tfrdu0.fsf@eliezer.anholt.net> <568C2619.20705@wwwdotorg.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:jFkWIDa9VBCE86os2t/zjLoJX0alMNzJwhSzEXNsFE4i5Q6dbWS CDQCow35yPLBwytt9ZUgcPXpMbmY2tjn7nSRgnEEvg9clEI5IEuiCrROJ2ZhHRW+XNbk3b2 ZfIfzxfTdBeBg+fohzpkrzUadt9CFaWxxuX4oIS/2y04kTgasQfWTIjpHSajV2fR5uCW3Wo /bsWxvPNMb4LemshEB3qQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:cDpUPy7WiqE=:uvmbGHR29fARGLwu/b6Nzc ZVxZo7VExc0kyto3/12mXqN8PPMhExuLD+UzHnTcJyRaQbPJKS7AkJuOKyfRIZCpEMcREQdYZ r6gohgMz5+ied6q5er1HyncPKYS7wwFVoZjPe2vDiFFMQRVv9pRLa3E3Y3xjgo4ZVKDKxguMa u0vZxz+qC+vaauATp7MmEofjH/zxkOt8rKkC5MkxNyoSNR56QXIar25VLfacH1XEl/75LeLtc 1E5KgcbVCiGveVa7mj29b056jNl/RiBif9gC26r4u2HXf1IXjn/9c1U0XIUXOViFQV/6R3IDZ xqqOVxGVOZYl+bIF2hCzucI5pxY01bj+Zad26xqPlBx5iiIoOCokmJMouDl118Gbdgcxt8PKV gvLu3+DLEoHpbNKQGa1DwfZiUo7nUEn9d0E67Ps1aFkE1Hcu980WfQQCLdXvp0OfuaiwYoxHF QKm5Jw9uskhPKPbjH7I78vJEz/dzgYk0JqfrrUAtv/HINyqJr3BTkD/jskBiIgEnVUAvY+Br7 cJdN2IA++h1F8ROZi+ser7rTRPkx56OLHHJV8FhGauJ0niMTZDUptXnVjEzBO9zuDXZWrqmZ0 3llCIVHpJCn1gz/N/XQhXWm5hNBpfsBG4sDLGuuMQFaLNBA56p4ChyyzLtXEEOsDRaXddEucK c8uZo15Gvgb9qszzeb0XNlYbLC8CJRyk0TN1C7M9pmtZIvnXZwubXdmKD9MAIy0RuqpMyaXlM xjN90ishdjsS0ixV Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 05 January 2016 13:22:49 Stephen Warren wrote: > >>> > >>> 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) > > Typically maintainers merge everything together into a single "for-next" > to maintain a reasonable set of branches. I guess it doesn't affect me > so my opinion isn't too relevant though:-) In my experience the common for-next branch works best because you can change the set of branches that get merged into it as needed. If there are 6 branches today, it's quite likely that there will be another one in the future and if only one branch gets merged into for-next, you don't need to worry about updating the list. Arnd