From: "Peng, Yuan" <yuan.peng@intel.com>
To: "Dai, Wei" <wei.dai@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Dai, Wei" <wei.dai@intel.com>
Subject: Re: [PATCH 0/4] update ixgbe base driver to version 2017-03-29
Date: Fri, 21 Apr 2017 03:50:20 +0000 [thread overview]
Message-ID: <67D543A150B29E4CAAE53918F64EDAEA373BA923@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1492498623-68509-1-git-send-email-wei.dai@intel.com>
Tested-by: Peng Yuan <yuan.peng@intel.com>
- Tested Branch: dpdk v17.02
- Tested Commit: b9ebab26d98f61bc407572623c4bee4390a8b432
- OS: 4.4.26-yocto-standard
- IFWI: HAVLCRB1.X64.0014.D76.1703170116
- NIC: Intel Corporation Device [8086:15ce] (rev 10)
driver: ixgbe-5.0.7
firmware-version: 0x800006f8/ 0x80000714
- Default x86_64-native-linuxapp-gcc configuration
- Prerequisites:
- Total 69 cases, 69 passed, 0 failed
You can check the test report from attachment.
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Dai
Sent: Tuesday, April 18, 2017 2:57 PM
To: Zhang, Helin <helin.zhang@intel.com>; Ananyev, Konstantin <konstantin.ananyev@intel.com>; Lu, Wenzhuo <wenzhuo.lu@intel.com>
Cc: dev@dpdk.org; Dai, Wei <wei.dai@intel.com>
Subject: [dpdk-dev] [PATCH 0/4] update ixgbe base driver to version 2017-03-29
This patch set has following 4 patches.
No any new device id is added.
net/ixgbe/base: acquire PHY semaphore before device reset
net/ixgbe/base: add support for 2.5G KX physical layer
net/ixgbe/base: add MAC X550em/X557 LED on/off support
net/ixgbe/base: update base driver version to 2017.03.29
drivers/net/ixgbe/base/README | 2 +-
drivers/net/ixgbe/base/ixgbe_82598.c | 4 ++-- drivers/net/ixgbe/base/ixgbe_82598.h | 2 +- drivers/net/ixgbe/base/ixgbe_82599.c | 4 ++-- drivers/net/ixgbe/base/ixgbe_82599.h | 2 +-
drivers/net/ixgbe/base/ixgbe_api.c | 2 +-
drivers/net/ixgbe/base/ixgbe_api.h | 2 +-
drivers/net/ixgbe/base/ixgbe_phy.c | 4 ++--
drivers/net/ixgbe/base/ixgbe_phy.h | 2 +-
drivers/net/ixgbe/base/ixgbe_type.h | 37 ++++++++++++++++++------------------
drivers/net/ixgbe/base/ixgbe_x540.c | 12 ++++++++++-- drivers/net/ixgbe/base/ixgbe_x540.h | 2 +- drivers/net/ixgbe/base/ixgbe_x550.c | 33 ++++++++++++++++++++++++++++---- drivers/net/ixgbe/base/ixgbe_x550.h | 2 +-
14 files changed, 72 insertions(+), 38 deletions(-)
--
2.7.4
next prev parent reply other threads:[~2017-04-21 3:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 6:56 [PATCH 0/4] update ixgbe base driver to version 2017-03-29 Wei Dai
2017-04-18 6:57 ` [PATCH 1/4] net/ixgbe/base: acquire PHY semaphore before device reset Wei Dai
2017-04-18 6:57 ` [PATCH 2/4] net/ixgbe/base: add support for 2.5G KX physical layer Wei Dai
2017-04-18 6:57 ` [PATCH 3/4] net/ixgbe/base: add MAC X550em/X557 LED on/off support Wei Dai
2017-04-18 6:57 ` [PATCH 4/4] net/ixgbe/base: update base driver version to 2017.03.29 Wei Dai
2017-04-19 13:22 ` [PATCH 0/4] update ixgbe base driver to version 2017-03-29 Ferruh Yigit
2017-04-20 13:29 ` Dai, Wei
2017-04-21 3:50 ` Peng, Yuan [this message]
2017-04-21 11:35 ` 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=67D543A150B29E4CAAE53918F64EDAEA373BA923@SHSMSX103.ccr.corp.intel.com \
--to=yuan.peng@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=wei.dai@intel.com \
--cc=wenzhuo.lu@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.