patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Li, Xiaoyun" <xiaoyun.li@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v2] doc: fix testpmd sample qinq flow rules
Date: Tue, 2 Feb 2021 09:59:57 +0000	[thread overview]
Message-ID: <09124987-e0ef-e798-4e99-4ab69564004d@intel.com> (raw)
In-Reply-To: <CY4PR11MB1750EFF5E9AAD6C6124BDF0E99A20@CY4PR11MB1750.namprd11.prod.outlook.com>

On 1/20/2021 1:42 AM, Li, Xiaoyun wrote:

>> -----Original Message-----
>> From: Iremonger, Bernard <bernard.iremonger@intel.com>
>> Sent: Tuesday, January 19, 2021 21:01
>> To: dev@dpdk.org; Li, Xiaoyun <xiaoyun.li@intel.com>
>> Cc: Iremonger, Bernard <bernard.iremonger@intel.com>; stable@dpdk.org
>> Subject: [PATCH v2] doc: fix testpmd sample qinq flow rules
>>
>> In the Testpmd Flow rules management section, correct the TPID values in the
>> Sample QinQ flow rules sub section.
>> Also replace the keyword qinq_strip with extend in the vlan set command.
>>
>> Fixes: bef3bfe7d5f4 ("doc: revise sample testpmd flow commands")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
 >
> Acked-by: Xiaoyun Li <xiaoyun.li@intel.com>
> 

Applied to dpdk-next-net/main, thanks.


      reply	other threads:[~2021-02-02 10:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1610623187-3631-1>
2021-01-19 13:00 ` Bernard Iremonger
2021-01-20  1:42   ` Li, Xiaoyun
2021-02-02  9:59     ` Ferruh Yigit [this message]

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=09124987-e0ef-e798-4e99-4ab69564004d@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --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).