From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Hemminger <stephen@networkplumber.org>
Subject: KNI - issues
Date: Sat, 20 Feb 2016 17:07:08 -0800
Message-ID: <20160220170708.37d0db29@xeon-e3>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
To: Helin Zhang <helin.zhang@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com
 [209.85.192.179]) by dpdk.org (Postfix) with ESMTP id 5A8B75690
 for <dev@dpdk.org>; Sun, 21 Feb 2016 06:00:32 +0100 (CET)
Received: by mail-pf0-f179.google.com with SMTP id x65so73957385pfb.1
 for <dev@dpdk.org>; Sat, 20 Feb 2016 21:00:32 -0800 (PST)
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Is anyone working on making KNI conform to current kernel best practices
and attempt to get it upstream?  After 2 minute code review I already
see lots and lots of things that need work.