From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <nhorman@tuxdriver.com>
Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58])
 by dpdk.org (Postfix) with ESMTP id AE04C5591
 for <dev@dpdk.org>; Mon, 12 Sep 2016 14:33:43 +0200 (CEST)
Received: from cpe-2606-a000-111b-40ed-7aac-c0ff-fec2-933b.dyn6.twc.com
 ([2606:a000:111b:40ed:7aac:c0ff:fec2:933b] helo=localhost)
 by smtp.tuxdriver.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63)
 (envelope-from <nhorman@tuxdriver.com>)
 id 1bjQQe-0006I3-HT; Mon, 12 Sep 2016 08:33:41 -0400
Date: Mon, 12 Sep 2016 08:33:32 -0400
From: Neil Horman <nhorman@tuxdriver.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>, dev@dpdk.org,
 Finn Christensen <fc@napatech.com>
Message-ID: <20160912123332.GC22847@hmsreliant.think-freely.org>
References: <20160908111424.14127-1-fc@napatech.com>
 <20160909135108.GA15908@hmsreliant.think-freely.org>
 <c5e8998f3e0d4a8e9a26b6457193795e@napatech.com>
 <1913786.NX7M2nQ5WY@xps13>
 <CAOaVG17qeHJQOx5Go07AFMjuxM9KcNRSEDgHYeaDKui9u7E6cw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOaVG17qeHJQOx5Go07AFMjuxM9KcNRSEDgHYeaDKui9u7E6cw@mail.gmail.com>
User-Agent: Mutt/1.7.0 (2016-08-17)
X-Spam-Score: -1.0 (-)
X-Spam-Status: No
Subject: Re: [dpdk-dev] [PATCH v3] ntnic: add PMD driver
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Sep 2016 12:33:43 -0000

On Sat, Sep 10, 2016 at 11:31:04AM -0700, Stephen Hemminger wrote:
> I think that if the driver is just a shim for proprietary code, then the
> vendor should just maintain it out of tree. 6wind and windriver already do
> this.
Agreed, this was my previous comment.  Someone probably wants this driver, but I
dont' want to maintain a shim.  Until its ready to be all open source, just
maintain it out of tree

Neil