From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752815AbdLLXne (ORCPT <rfc822;w@1wt.eu>);
        Tue, 12 Dec 2017 18:43:34 -0500
Received: from bombadil.infradead.org ([65.50.211.133]:58938 "EHLO
        bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752723AbdLLXnb (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 12 Dec 2017 18:43:31 -0500
Date: Tue, 12 Dec 2017 15:43:30 -0800
From: Darren Hart <dvhart@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: the drivers-x86 tree has moved?
Message-ID: <20171212234330.GK27831@fury>
References: <20171213080227.7b724f39@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171213080227.7b724f39@canb.auug.org.au>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Dec 13, 2017 at 08:02:27AM +1100, Stephen Rothwell wrote:
> Hi Darren,
> 
> I noticed commit
> 
>   960652046899 ("MAINTAINERS: Update tree for platform-drivers-x86")
> 
> Should I also change linu-next to use the new tree?

The new one is the correct location, but the old one points to it. I don't plan
to destroy the old link, but updating linux-next to use the new one is a good
idea.

So, yes - please do :-)

-- 
Darren Hart
VMware Open Source Technology Center