From: Thomas Monjalon <thomas@monjalon.net>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Pei, Yulong" <yulong.pei@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: revise sample testpmd flow commands
Date: Mon, 01 May 2017 22:39:33 +0200 [thread overview]
Message-ID: <2549617.gZERfVA65J@xps> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2332C2A29@IRSMSX103.ger.corp.intel.com>
> > Stop port before enabling QinQ.
> > Add commands to set inner and outer TPID's and start port.
> > Remove TPID's from flow validate and and flow create commands.
> >
> > Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-05-01 20:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 14:20 Bernard Iremonger
2017-04-26 15:04 ` Mcnamara, John
2017-05-01 20:39 ` Thomas Monjalon [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=2549617.gZERfVA65J@xps \
--to=thomas@monjalon.net \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=yulong.pei@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).