From: Stephen Hemminger <stephen@networkplumber.org>
To: Helin Zhang <helin.zhang@intel.com>
Cc: dev@dpdk.org
Subject: KNI - issues
Date: Sat, 20 Feb 2016 17:07:08 -0800 [thread overview]
Message-ID: <20160220170708.37d0db29@xeon-e3> (raw)
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.
next reply other threads:[~2016-02-21 5:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 1:07 Stephen Hemminger [this message]
2016-02-22 2:44 ` KNI - issues Zhang, Helin
2016-02-22 14:00 ` Ferruh Yigit
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160220170708.37d0db29@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.