From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] IMPORTANT: feature freeze for version 1.7.0
Date: Sun, 1 Jun 2014 14:26:49 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F9625117C75E8@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <2310674.RXXT23nrXG@xps13>
Hi Thomas,
For the item "the link up/down",
Its subject is changed from "Support administrative link up and link down"
into "Support setting link up and link down" according to Ivan's comments.
And the v2 patch for it is also be acked by Ivan, please see the attachment.
Wish you have a happy vacation! :-)
Thanks very much and best regards,
Changchun
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Friday, May 30, 2014 9:12 PM
To: dev@dpdk.org
Subject: [dpdk-dev] IMPORTANT: feature freeze for version 1.7.0
Hello all,
We have a lot of new features mostly ready for DPDK 1.7.0.
It's now time to be sure that they are well reviewed and integrated.
Then release candidate should be tagged in mid-June in order to have some validation tests before end of June (planned released date).
So requests for integration of features which have not yet been sent will be delayed to next version. Only reworks or small fixes of pending patches should be accepted.
A new branch "rebased-next" will be created for patches which are reviewed and waiting next version. This branch will be regularly rebased on master HEAD.
Being currently on vacation, I won't be very active until Monday, 9th.
During this time, I'd like to see some reviews/acknowledgements for these
patches:
- socket id detection fallback
http://dpdk.org/ml/archives/dev/2014-April/001987.html
- fix rte_free run time in O(n) free blocks
http://dpdk.org/ml/archives/dev/2014-May/002296.html
- fix mbuf corruption in pcap_tx
http://dpdk.org/ml/archives/dev/2014-May/002919.html
- igb_uio fixes
http://dpdk.org/ml/archives/dev/2014-May/002428.html
- vfio
http://dpdk.org/ml/archives/dev/2014-May/002914.html
- ethernet enhancements
http://dpdk.org/ml/archives/dev/2014-May/002436.html
- splitted statistics
http://dpdk.org/ml/archives/dev/2014-May/002707.html
- mtu/flow control
http://dpdk.org/ml/archives/dev/2014-May/002752.html
- link up/down
http://dpdk.org/ml/archives/dev/2014-May/002660.html
- Tx rate limitation
http://dpdk.org/ml/archives/dev/2014-May/002696.html
- lpm optimization
http://dpdk.org/ml/archives/dev/2014-May/002703.html
- generic filter
http://dpdk.org/ml/archives/dev/2014-May/002740.html
http://dpdk.org/ml/archives/dev/2014-May/002577.html
- ip_frag
http://dpdk.org/ml/archives/dev/2014-May/002930.html
- distributor
http://dpdk.org/ml/archives/dev/2014-May/002598.html
- link bonding
http://dpdk.org/ml/archives/dev/2014-May/002922.html
- acl
http://dpdk.org/ml/archives/dev/2014-May/002945.html
- packet framework
http://dpdk.org/ml/archives/dev/2014-May/002820.html
Thanks for your participation
--
Thomas
next prev parent reply other threads:[~2014-06-01 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 13:11 Thomas Monjalon
2014-06-01 14:26 ` Ouyang, Changchun [this message]
2014-06-02 13:45 ` Dumitrescu, Cristian
2014-06-02 15:04 ` Neil Horman
2014-06-09 5:54 ` Cao, Waterman
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=F52918179C57134FAEC9EA62FA2F9625117C75E8@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).