From: lijuan.tu@intel.com
To: dts@dpdk.org,Yaqi Tang <yaqi.tang@intel.com>
Cc: Yaqi Tang <yaqi.tang@intel.com>
Subject: [dts][PATCH V2 2/2] tests/cvl_iavf_fdir_pppol2tpoudp: modify test script for more fdir action
Date: 10 Apr 2022 19:53:59 -0700 [thread overview]
Message-ID: <8ea9f5$kqpnui@fmsmga001-auth.fm.intel.com> (raw)
In-Reply-To: <20220406142311.384595-3-yaqi.tang@intel.com>
On Wed, 6 Apr 2022 22:23:11 +0800, Yaqi Tang <yaqi.tang@intel.com> wrote:
> The previous actions were only queue index and add several actions.
>
> Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
Series applied, thanks
prev parent reply other threads:[~2022-04-11 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 14:23 [dts][PATCH V2 0/2] Modify fdir pppol2tpoudp test plan and script Yaqi Tang
2022-04-06 14:23 ` [dts][PATCH V2 1/2] test_plans/cvl_iavf_fdir_pppol2tpoudp: modify test plan for more fdir action Yaqi Tang
2022-04-06 14:23 ` [dts][PATCH V2 2/2] tests/cvl_iavf_fdir_pppol2tpoudp: modify test script " Yaqi Tang
2022-04-11 2:53 ` lijuan.tu [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='8ea9f5$kqpnui@fmsmga001-auth.fm.intel.com' \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=yaqi.tang@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).