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: Mon, 25 May 2020 16:55:54 +0100 [thread overview]
Message-ID: <16c9a6ec-ec9a-43b9-386b-3255ed7b0420@intel.com> (raw)
In-Reply-To: <BYAPR11MB3541D6128FC7B7167C066750F7B30@BYAPR11MB3541.namprd11.prod.outlook.com>
On 5/25/2020 3:03 AM, Xing, Beilei wrote:
>
>
>> -----Original Message-----
>> From: Yigit, Ferruh <ferruh.yigit@intel.com>
>> Sent: Friday, May 22, 2020 11:31 PM
>> To: Xing, Beilei <beilei.xing@intel.com>; Chen, Zhaoyan
>> <zhaoyan.chen@intel.com>; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v1]doc:Update i40e PMD firmware/driver
>> mapping table.
>>
>> 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.
>>
>
> Yes, thanks.
>
> Except the minor comments,
> Acked-by: Beilei Xing <beilei.xing@intel.com>
>
(Used suggested title.)
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2020-05-25 15:55 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
2020-05-25 2:03 ` Xing, Beilei
2020-05-25 2:30 ` Chen, Zhaoyan
2020-05-25 15:55 ` Ferruh Yigit [this message]
-- 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=16c9a6ec-ec9a-43b9-386b-3255ed7b0420@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).