From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Fu, Qi" <qi.fu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Fu, Qi" <qi.fu@intel.com>
Subject: Re: [dts] [PATCH V1]test_plans/cvl_advanced_rss_gtpu_test_plan:update GTPPDUSessionContainer layer and some steps
Date: Wed, 11 Nov 2020 03:29:45 +0000 [thread overview]
Message-ID: <d3b5abe07ce44a7d94bc5b1b8c36f227@intel.com> (raw)
In-Reply-To: <20201104153531.21975-1-qi.fu@intel.com>
> 1. use the scapy layer GTPPDUSessionContainer instead of local layer
> GTP_PDUSession_ExtensionHeader in gtpu test plan.
> 2. fix typo in Subcase: toeplitz/symmetric with same pattern (switched rule
> order)
> 3. modify expected result in Subcase: toeplitz/symmetric with different
> pattern (with/without UL/DL)
> as code changing.
>
> Signed-off-by: qifu <qi.fu@intel.com>
Applied
prev parent reply other threads:[~2020-11-11 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 15:35 qifu
2020-11-11 3:29 ` Tu, Lijuan [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=d3b5abe07ce44a7d94bc5b1b8c36f227@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=qi.fu@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).