From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <helin.zhang@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id C93A158DF
 for <dev@dpdk.org>; Mon, 22 Feb 2016 03:44:51 +0100 (CET)
Received: from fmsmga003.fm.intel.com ([10.253.24.29])
 by orsmga101.jf.intel.com with ESMTP; 21 Feb 2016 18:44:49 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,483,1449561600"; d="scan'208";a="656878919"
Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201])
 by FMSMGA003.fm.intel.com with ESMTP; 21 Feb 2016 18:44:51 -0800
Received: from fmsmsx114.amr.corp.intel.com (10.18.116.8) by
 FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Sun, 21 Feb 2016 18:44:49 -0800
Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by
 FMSMSX114.amr.corp.intel.com (10.18.116.8) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Sun, 21 Feb 2016 18:44:49 -0800
Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.112]) by
 SHSMSX151.ccr.corp.intel.com ([169.254.3.196]) with mapi id 14.03.0248.002;
 Mon, 22 Feb 2016 10:44:47 +0800
From: "Zhang, Helin" <helin.zhang@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Thread-Topic: KNI - issues
Thread-Index: AQHRbEQza1freMwyQ0eZK11u+vsvu583XPOw
Date: Mon, 22 Feb 2016 02:44:46 +0000
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A9AA046@SHSMSX104.ccr.corp.intel.com>
References: <20160220170708.37d0db29@xeon-e3>
In-Reply-To: <20160220170708.37d0db29@xeon-e3>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ctpclassification: CTP_IC
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiODFiMTNhYzQtMzQ5My00Y2UzLWIzNWEtNDkzOWNlY2ZkNjRiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiQmQ0bHZFUzF0bDEwNm1rQ3RpdkhZXC8rR2d5enh0cE9JZVAxWVBUVzh6bms9In0=
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI - issues
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, 22 Feb 2016 02:44:52 -0000

Hi Stephen

I don't think so. I'd ask internally to see if somebody can help on that.
Thanks and sorry!

Regards,
Helin

> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Sunday, February 21, 2016 9:07 AM
> To: Zhang, Helin <helin.zhang@intel.com>
> Cc: dev@dpdk.org
> Subject: KNI - issues
>=20
> 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 lot=
s and
> lots of things that need work.