From: Yuanhan Liu <yliu@fridaylinux.org>
To: dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org
Subject: [dpdk-stable] 17.05.1 patches review and test
Date: Thu, 22 Jun 2017 21:08:25 +0800 [thread overview]
Message-ID: <20170622130825.GB7605@yliu-home> (raw)
Hi all,
I'm doing an unexpected stable release, which is expected to be released
in about two months. The reason I'm doing it is there is an import bug
fix commit that is needed for OVS 2.8 release. The fix is a vhost-user
commit comes from me. Well, unfortunately, I'm also the author of the
original bug :/
So I'm doing an urgent release. That also means we will have another
17.05 release (17.05.2) shortly after v17.08 is out.
And here is a list of patches targeted for this release. Please help
review and test. The planned date for the final release is 30, June.
Before that, please shout if anyone has objections.
These patches are located at branch 17.05 of dpdk-stable repo:
http://dpdk.org/browse/dpdk-stable/
Thanks.
--yliu
---
Ajit Khaparde (1):
net/bnxt: fix reporting of link status
Alejandro Lucero (1):
vfio: fix array bounds check
Andrew Rybchenko (1):
net/sfc: add Tx queue flush failed flag for sanity
Andy Moreton (2):
net/sfc/base: fix error code usage in common code
net/sfc/base: let caller know that queue is already flushed
Beilei Xing (1):
app/testpmd: fix creating E-Tag and NVGRE flow rules
Chas Williams (3):
net/af_packet: handle possible null pointer
net/af_packet: fix packet bytes counting
net/ring: fix adding MAC addresses
Dariusz Stojaczyk (2):
vhost: fix malloc size too small
vhost: fix guest pages memory leak
David Marchand (1):
drivers/net: fix vfio kmod dependency
Ferruh Yigit (3):
kni: fix build with gcc 7.1
net/enic: fix build with gcc 7.1
net/mlx5: fix build with gcc 7.1
Harish Patil (1):
net/qede: fix VXLAN tunnel Tx offload flag setting
Jerin Jacob (1):
examples/vhost: fix uninitialized descriptor indexes
John Miller (4):
net/ark: fix buffer not null terminated
net/ark: fix return code not checked
net/ark: fix null pointer dereference
net/ark: fix return value of null not checked
Lee Roberts (1):
kni: fix build on RHEL 7.4
Markus Theil (1):
net/igb: fix add/delete of flex filters
Nélio Laranjeiro (1):
net/mlx5: fix flow application order on stop/start
Pascal Mazon (1):
net/tap: fix some flow collision
Qi Zhang (3):
net/ixgbe: fix fdir mask not be reset
net/i40e: exclude internal packet's byte count
net/i40e: fix VF statistics
Rahul Lakkireddy (2):
net/cxgbe: fix port statistics
net/cxgbe: fix rxq default params for ports under same PF
Shahaf Shuler (1):
net/mlx5: fix completion buffer size
Shijith Thotton (1):
net/liquidio: fix MTU calculation from port configuration
Tiwei Bie (1):
net/virtio: zero the whole memory zone
Wei Dai (1):
lpm: fix index of tbl8
Wei Zhao (1):
net/igb: fix checksum valid flags
Wenzhuo Lu (1):
net/i40e/base: fix Tx error stats on VF
Yongseok Koh (2):
net/mlx5: fix exception handling
net/mlx5: fix redundant free of Tx buffer
Yuanhan Liu (1):
vhost: fix crash on NUMA
next reply other threads:[~2017-06-22 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 13:08 Yuanhan Liu [this message]
2017-06-28 12:49 ` [dpdk-stable] [dpdk-dev] " Kavanagh, Mark B
2017-06-29 1:31 ` Chen, WeichunX
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=20170622130825.GB7605@yliu-home \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).