From: Stephen Hemminger <stephen@networkplumber.org>
To: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Why nothing since 1.8.0?
Date: Sat, 17 Jan 2015 16:30:51 -0800 [thread overview]
Message-ID: <CAOaVG14+0vOPaOh=4ajLn6jGxJgFzAmd9Fz=Rr=XfBjaDgT9eg@mail.gmail.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54CA4BCC@IRSMSX102.ger.corp.intel.com>
I am all for having multiple staging trees that get MERGED into one
upstream tree.
Let me make it simple, no out of tree drivers. I am not supporting,
maintaining or submitting drivers that
are not in the mainline DPDK product. If you want me to submit drivers,
then they should go into
the mainstream.
Developers:
Want to be able to make changes to core infrastructure during merge window
and fix all the
related drivers. For many devices, developer wants to be able to submit a
driver and have it
fixed by others in the main tree.
Vendors:
Want to be able to extend, change, and enhance the existing DPDK tree and
then build an application
with that. It is a increase in technical overhead to merge in drivers from
multiple sources.
next prev parent reply other threads:[~2015-01-18 0:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 20:23 Stephen Hemminger
2015-01-14 21:01 ` Neil Horman
2015-01-15 4:15 ` Zhang, Helin
2015-01-15 4:27 ` Ouyang, Changchun
2015-01-15 9:51 ` Thomas Monjalon
2015-01-15 13:06 ` Neil Horman
2015-01-15 17:25 ` Thomas Monjalon
2015-01-15 18:51 ` Neil Horman
2015-01-15 21:55 ` O'driscoll, Tim
2015-01-16 1:46 ` Matthew Hall
2015-01-16 7:16 ` Thomas Monjalon
2015-01-16 16:51 ` Neil Horman
2015-01-17 19:57 ` O'driscoll, Tim
2015-01-18 0:30 ` Stephen Hemminger [this message]
[not found] ` <20150118182508.GA21891@hmsreliant.think-freely.org>
2015-01-18 21:48 ` O'driscoll, Tim
2015-01-19 13:30 ` Neil Horman
2015-01-15 22:23 ` Thomas Monjalon
2015-01-16 17:20 ` Neil Horman
2015-01-16 18:18 ` Thomas Monjalon
2015-01-16 18:58 ` Matthew Hall
2015-01-16 20:00 ` Neil Horman
2015-01-16 20:38 ` Matthew Hall
2015-01-16 21:14 ` Neil Horman
2015-01-16 22:43 ` Matthew Hall
2015-01-16 19:53 ` Neil Horman
2015-01-16 14:51 ` Marc Sune
2015-01-16 16:56 ` Neil Horman
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='CAOaVG14+0vOPaOh=4ajLn6jGxJgFzAmd9Fz=Rr=XfBjaDgT9eg@mail.gmail.com' \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=tim.o'driscoll@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).