From: "Cao, Min" <min.cao@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] fix of lsc interrupt in i40e PF
Date: Tue, 30 Sep 2014 06:09:14 +0000 [thread overview]
Message-ID: <B6059B2012717B4390714544B1F509E110D798FB@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1410940461-17509-1-git-send-email-helin.zhang@intel.com>
Tested-by: Min Cao <min.cao@intel.com>
This patch has been verified on FC20 with Eagle Fountain: 4*10G .
The i40e base driver update patch works well on FC20 with basic function.
The test environment detail information as the following:
HOST environment:
CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
OS: Linux 3.11.10
GCC: 4.8.3
NIC: Eagle Fountain: 4*10G
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Helin Zhang
Sent: Wednesday, September 17, 2014 3:54 PM
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] fix of lsc interrupt in i40e PF
The patches include the fix for link status change interrupt
in i40e PF, and code style fixes.
Helin Zhang (3):
i40e: renaming some local variables
i40e: rework of PF interrupt cause enable flags processing
i40e: fix of interrupt based link status change
lib/librte_pmd_i40e/i40e_ethdev.c | 174 ++++++++++++++++++++++++++------------
1 file changed, 122 insertions(+), 52 deletions(-)
--
1.8.1.4
next prev parent reply other threads:[~2014-09-30 6:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 7:54 Helin Zhang
2014-09-17 7:54 ` [dpdk-dev] [PATCH 1/3] i40e: renaming some local variables Helin Zhang
2014-09-17 7:54 ` [dpdk-dev] [PATCH 2/3] i40e: rework of PF interrupt cause enable flags processing Helin Zhang
2014-09-17 7:54 ` [dpdk-dev] [PATCH 3/3] i40e: fix of interrupt based link status change Helin Zhang
2014-09-30 6:09 ` Cao, Min [this message]
2014-10-10 1:48 ` [dpdk-dev] [PATCH 0/3] fix of lsc interrupt in i40e PF Chen, Jing D
2014-11-03 17:19 ` Thomas Monjalon
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=B6059B2012717B4390714544B1F509E110D798FB@SHSMSX103.ccr.corp.intel.com \
--to=min.cao@intel.com \
--cc=dev@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).