From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Xing, Beilei" <beilei.xing@intel.com>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1]doc:Update i40e PMD firmware/driver mapping table.
Date: Fri, 22 May 2020 16:30:42 +0100 [thread overview]
Message-ID: <3a72f938-fb00-1160-af6c-2b7ace199949@intel.com> (raw)
In-Reply-To: <BYAPR11MB35414EB231B992FA6A6C8D48F7B40@BYAPR11MB3541.namprd11.prod.outlook.com>
On 5/22/2020 3:20 AM, Xing, Beilei wrote:
>
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Chen, Zhaoyan
>> Sent: Thursday, May 21, 2020 3:45 PM
>> To: dev@dpdk.org
>> Cc: Chen, Zhaoyan <zhaoyan.chen@intel.com>
>> Subject: [dpdk-dev] [PATCH v1]doc:Update i40e PMD firmware/driver
>> mapping table.
>
> Minor comments:
> 1. Space is needed after colon
> 2. Update -> update
> 3. no need . in the tile
> So it should be like "doc: update firmware/driver mapping table for i40e"
Hi Beilei,
If the content is correct and only issue is above ones, I can fix them while
merging.
>
>>
>> Update i40e PMD firmware/driver mapping table.
>>
>> Signed-off-by: Zhaoyan Chen <zhaoyan.chen@intel.com>
>>
>> ---
>> doc/guides/nics/i40e.rst | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst index
>> 2f846091cf..00c3042d5d 100644
>> --- a/doc/guides/nics/i40e.rst
>> +++ b/doc/guides/nics/i40e.rst
>> @@ -88,6 +88,8 @@ For X710/XL710/XXV710,
>> +--------------+-----------------------+------------------+
>> | DPDK version | Kernel driver version | Firmware version |
>> +==============+=======================+==================+
>> + | 20.05 | 2.11.27 | 7.30 |
>> + +--------------+-----------------------+------------------+
>> | 20.02 | 2.10.19 | 7.20 |
>> +--------------+-----------------------+------------------+
>> | 19.11 | 2.9.21 | 7.00 |
>> @@ -127,6 +129,8 @@ For X722,
>> +--------------+-----------------------+------------------+
>> | DPDK version | Kernel driver version | Firmware version |
>> +==============+=======================+==================+
>> + | 20.05 | 2.11.27 | 4.11 |
>> + +--------------+-----------------------+------------------+
>> | 20.02 | 2.10.19 | 4.11 |
>> +--------------+-----------------------+------------------+
>> | 19.11 | 2.9.21 | 4.10 |
>> --
>> 2.22.0
>
next prev parent reply other threads:[~2020-05-22 15:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 7:45 Chen, Zhaoyan
2020-05-22 2:20 ` Xing, Beilei
2020-05-22 15:30 ` Ferruh Yigit [this message]
2020-05-25 2:03 ` Xing, Beilei
2020-05-25 2:30 ` Chen, Zhaoyan
2020-05-25 15:55 ` Ferruh Yigit
-- strict thread matches above, loose matches on Subject: below --
2020-05-21 7:43 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=3a72f938-fb00-1160-af6c-2b7ace199949@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--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).