From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [PATCH v9] net/kni: add KNI PMD
Date: Fri, 17 Feb 2017 14:29:51 +0000
Message-ID: <86596f35-f483-e493-101e-f93969bd2f1b@intel.com>
References: <20170131121819.32196-1-ferruh.yigit@intel.com>
 <20170217134238.27064-1-ferruh.yigit@intel.com> <1566055.VXsRebtFXA@xps13>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
 Yong Wang <yongwang@vmware.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31])
 by dpdk.org (Postfix) with ESMTP id 758E2952
 for <dev@dpdk.org>; Fri, 17 Feb 2017 15:29:55 +0100 (CET)
In-Reply-To: <1566055.VXsRebtFXA@xps13>
List-Id: DPDK patches and discussions <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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 2/17/2017 1:47 PM, Thomas Monjalon wrote:
> 2017-02-17 13:42, Ferruh Yigit:
>> Add KNI PMD which wraps librte_kni for ease of use.
>>
>> KNI PMD can be used as any regular PMD to send / receive packets to the
>> Linux networking stack.
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> Reviewed-by: Yong Wang <yongwang@vmware.com>
>> ---
>>
>> v9:
>> * update for 17.05
> 
> You keep updating this patch in the hope that someone would be interested :)
> 
> Please let's make clear that I am OK to merge it
> but you asked me to wait for someone supporting its inclusion.

Right, it is good to mention that I explicitly asked to wait community
response.

I keep updating it because I believe this is something useful.

Meanwhile adding this into repo means maintenance cost, so this should
not be merged without any usecase or interest from community.

Patch is waiting for an ACK or NAK from community.

Thanks,
ferruh