From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: dev@dpdk.org, Chen@dpdk.org
Subject: Re: [dpdk-dev] [PATCH V1] doc:Split recommended mapping table for X710/XL710/XXV710 and X722, since they have different firmware version.
Date: Tue, 11 Feb 2020 10:34:22 +0800 [thread overview]
Message-ID: <20200211023422.GI80720@intel.com> (raw)
In-Reply-To: <20200204033509.144827-1-zhaoyan.chen@intel.com>
Subject is too long, should be something like:
doc: split recommended mapping table
On 02/04, Chen, Zhaoyan wrote:
>Split recommended mapping table for X710/XL710/XXV710 and X722,
>since they have different firmware version.
>
>Signed-off-by: Chen, Zhaoyan <zhaoyan.chen@intel.com>
DPDK convention for the SoB should be:
Signed-off-by: Zhaoyan Chen <zhaoyan.chen@intel.com>
>---
> doc/guides/nics/i40e.rst | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
>diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
>index c7c34b62f..4292375d9 100644
>--- a/doc/guides/nics/i40e.rst
>+++ b/doc/guides/nics/i40e.rst
>@@ -66,6 +66,8 @@ avoid the compatibility issues with i40e PMD. Here is the suggested matching
> list which has been tested and verified. The detailed information can refer
> to chapter Tested Platforms/Tested NICs in release notes.
>
>+For X710/XL710/XXV710,
>+
> +--------------+-----------------------+------------------+
> | DPDK version | Kernel driver version | Firmware version |
> +==============+=======================+==================+
>@@ -100,6 +102,24 @@ to chapter Tested Platforms/Tested NICs in release notes.
> | 16.04 | 1.4.25 | 5.02 |
> +--------------+-----------------------+------------------+
>
>+
>+For X722,
>+
>+ +--------------+-----------------------+------------------+
>+ | DPDK version | Kernel driver version | Firmware version |
>+ +==============+=======================+==================+
>+ | 19.11 | 2.9.21 | 4.10 |
>+ +--------------+-----------------------+------------------+
>+ | 19.08 | 2.9.21 | 4.10 |
>+ +--------------+-----------------------+------------------+
>+ | 19.05 | 2.7.29 | 3.33 |
>+ +--------------+-----------------------+------------------+
>+ | 19.02 | 2.7.26 | 3.33 |
>+ +--------------+-----------------------+------------------+
>+ | 18.11 | 2.4.6 | 3.33 |
>+ +--------------+-----------------------+------------------+
>+
>+
> Pre-Installation Configuration
> ------------------------------
>
>--
>2.22.0
>
Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>
Applied to dpdk-next-net-intel with above fixes, Thanks.
next prev parent reply other threads:[~2020-02-11 2:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 3:35 Chen, Zhaoyan
2020-02-11 2:34 ` Ye Xiaolong [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-04 3:29 Chen, Zhaoyan
2020-02-04 3:23 Chen, Zhaoyan
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=20200211023422.GI80720@intel.com \
--to=xiaolong.ye@intel.com \
--cc=Chen@dpdk.org \
--cc=dev@dpdk.org \
--cc=zhaoyan.chen@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).