From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754431AbcFGXKc (ORCPT ); Tue, 7 Jun 2016 19:10:32 -0400 Received: from ozlabs.org ([103.22.144.67]:45019 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752313AbcFGXK3 (ORCPT ); Tue, 7 Jun 2016 19:10:29 -0400 Date: Wed, 8 Jun 2016 09:10:27 +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: <20160608091027.4e7d792e@canb.auug.org.au> In-Reply-To: <8737oo64ud.fsf@eliezer.anholt.net> References: <87wpm22co5.fsf@eliezer.anholt.net> <20160607093928.11a82881@canb.auug.org.au> <8737oo64ud.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 Tue, 07 Jun 2016 14:56:10 -0700 Eric Anholt wrote: > > In next-20160607 I see drm-vc4-next merged separately, which I also > included in for-next. I think it would be best to drop that one, too. OK, I was assuming that it was being merged via the drm tree. I will drop it today. -- Cheers, Stephen Rothwell