From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Steven J. Hill" <Steven.Hill@cavium.com>
Subject: Re: [PATCH net-next v9 0/4] Prerequisites for Cavium OCTEON-III
 network driver.
Date: Wed, 2 May 2018 13:19:24 -0500
Message-ID: <90c94fc2-b69d-fd22-40ec-e9344e72768d@cavium.com>
References: <1524785414-19236-1-git-send-email-steven.hill@cavium.com>
 <20180429.203347.679522174405836744.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org
To: David Miller <davem@davemloft.net>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-dm3nam03on0078.outbound.protection.outlook.com ([104.47.41.78]:35648
        "EHLO NAM03-DM3-obe.outbound.protection.outlook.com"
        rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP
        id S1750947AbeEBSTa (ORCPT <rfc822;netdev@vger.kernel.org>);
        Wed, 2 May 2018 14:19:30 -0400
In-Reply-To: <20180429.203347.679522174405836744.davem@davemloft.net>
Content-Language: en-US
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 04/29/2018 07:33 PM, David Miller wrote:
> 
> I don't know if we really want all of these MIPS specific changes to
> go via the net-next tree.
> 
> The right way to do this is probably getting this series into the MIPS
> architecture tree.
> 
David,

Correct, and I should have been clearer about that. The MIPS-specific
changes are targeted for 4.18 and I will be working with James/Ralf
to get those in. The actual changes for adding the driver, however,
should be fine to go into net-next. The netdev list should have been
a CC: for those patches and the Linux/MIPS mailing list as the main
recipient. Mea culpa.

Steve