From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753139AbcFFXjb (ORCPT ); Mon, 6 Jun 2016 19:39:31 -0400 Received: from ozlabs.org ([103.22.144.67]:41672 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752471AbcFFXja (ORCPT ); Mon, 6 Jun 2016 19:39:30 -0400 Date: Tue, 7 Jun 2016 09:39:28 +1000 From: Stephen Rothwell To: Eric Anholt Cc: linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Florian Fainelli , Stephen Warren Subject: Re: Updating Raspberry Pi trees pulled for -next Message-ID: <20160607093928.11a82881@canb.auug.org.au> In-Reply-To: <87wpm22co5.fsf@eliezer.anholt.net> References: <87wpm22co5.fsf@eliezer.anholt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Eric, On Mon, 06 Jun 2016 15:08:26 -0700 Eric Anholt wrote: > > I was going to bother you to add a bunch more trees to pull into -next > now that I'll be merging arm64 changes for the Raspberry Pi 3, but > instead I've decided to start using the maint-scripts to make generating > a single for-next branch trivial. Thanks for that. > So, could you replace all of my -next branches you're pulling with: > > git://github.com/anholt/linux.git#for-next Done. -- Cheers, Stephen Rothwell