From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Li, Xiaoyun" <xiaoyun.li@intel.com>, Ori Kam <orika@nvidia.com>,
Bing Zhao <bingz@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: fix formatting in testpmd user guide
Date: Tue, 27 Apr 2021 13:03:30 +0100 [thread overview]
Message-ID: <d59c0407-16c3-f40c-8f31-42e2fb2af318@intel.com> (raw)
In-Reply-To: <DM4PR11MB5534360C6C377A2C8F61240B99439@DM4PR11MB5534.namprd11.prod.outlook.com>
On 4/25/2021 2:53 AM, Li, Xiaoyun wrote:
> Hi
>
>> -----Original Message-----
>> From: Yigit, Ferruh <ferruh.yigit@intel.com>
>> Sent: Saturday, April 24, 2021 00:30
>> To: Li, Xiaoyun <xiaoyun.li@intel.com>; Ori Kam <orika@nvidia.com>; Bing Zhao
>> <bingz@nvidia.com>
>> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; dev@dpdk.org; Ajit Khaparde
>> <ajit.khaparde@broadcom.com>
>> Subject: [PATCH v2] doc: fix formatting in testpmd user guide
>>
>> From: Ajit Khaparde <ajit.khaparde@broadcom.com>
>>
>> Fix formatting in testpmd user guide for hairpin operation.
>>
>> Fixes: 01817b10d27c ("app/testpmd: change hairpin queues setup")
>> Cc:stable@dpdk.org
>
> Missing a space after "Cc:" as patchwork says.
>
> Except for this typo,
> Acked-by: Xiaoyun Li <xiaoyun.li@intel.com>
>
Applied to dpdk-next-net/main, thanks.
Typo fixed while merging.
next prev parent reply other threads:[~2021-04-27 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 22:34 [dpdk-dev] [PATCH] " Ajit Khaparde
2021-03-09 12:52 ` Ferruh Yigit
2021-03-09 22:00 ` Ajit Khaparde
2021-03-26 10:00 ` Ferruh Yigit
2021-04-13 16:18 ` Ferruh Yigit
2021-04-23 16:29 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2021-04-25 1:53 ` Li, Xiaoyun
2021-04-27 12:03 ` Ferruh Yigit [this message]
2021-04-25 6:12 ` Bing Zhao
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=d59c0407-16c3-f40c-8f31-42e2fb2af318@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=xiaoyun.li@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).