From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
"Zhang, Helin" <helin.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v7 0/2] net/i40e: enable 25G device
Date: Tue, 27 Sep 2016 08:57:57 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F80E2732E2@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1474940242-40426-1-git-send-email-qi.z.zhang@intel.com>
> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Tuesday, September 27, 2016 9:37 AM
> To: Wu, Jingjing; Zhang, Helin
> Cc: dev@dpdk.org; Zhang, Qi Z
> Subject: [PATCH v7 0/2] net/i40e: enable 25G device
>
> The patch enable devices that support 25G link speed.
> It is based on previous 25G base driver update:
> http://dpdk.org/ml/archives/dev/2016-August/045569.html
>
>
> v7:
> - 25G device is XXV710 not XXL710, correct it.
>
> v6:
> - rebase to dpdk-next-net/rel_16_11.
>
> v5:
> - no chnage, just for adding the missing change log.
>
> v4:
> - correct return value check of i40e_dev_sync_phy_type.
>
> v3:
> - use PHY type to check PHY capability.
> - change the commit log in PATCH 1/2.
>
> v2:
> - remove some tailing white space.
>
> Zhang Qi (2):
> net/i40e: use PHY type to check PHY capability
> net/i40e: enable 25G device
>
> drivers/net/i40e/i40e_ethdev.c | 53
> +++++++++++++++++++++++++++++++++++-------
> drivers/net/i40e/i40e_ethdev.h | 14 +++++++++++
> 2 files changed, 59 insertions(+), 8 deletions(-)
>
> --
> 2.7.4
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
Thanks
Jingjing
next prev parent reply other threads:[~2016-09-27 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 1:37 Zhang Qi
2016-09-27 1:37 ` [dpdk-dev] [PATCH v7 1/2] net/i40e: use PHY type to check PHY capability Zhang Qi
2016-09-27 1:37 ` [dpdk-dev] [PATCH v7 2/2] net/i40e: enable 25G device Zhang Qi
2016-09-27 8:57 ` Wu, Jingjing [this message]
2016-09-27 14:43 ` [dpdk-dev] [PATCH v7 0/2] " Bruce Richardson
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=9BB6961774997848B5B42BEC655768F80E2732E2@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=qi.z.zhang@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).