From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "An, XiangX" <xiangx.an@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Lin, Xueqin" <xueqin.lin@intel.com>, "An, XiangX" <xiangx.an@intel.com>
Subject: Re: [dts] [PATCH V1 0/2] dynamic_flowtype: remove a cmd to adapt dpdk
Date: Wed, 9 Jun 2021 07:12:19 +0000 [thread overview]
Message-ID: <8ca6a4dd800445c7a2d09c6c93a4cd23@intel.com> (raw)
In-Reply-To: <1622620919-59787-1-git-send-email-xiangx.an@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Xiang An
> Sent: 2021年6月2日 16:02
> To: dts@dpdk.org
> Cc: Lin, Xueqin <xueqin.lin@intel.com>; An, XiangX <xiangx.an@intel.com>
> Subject: [dts] [PATCH V1 0/2] dynamic_flowtype: remove a cmd to adapt dpdk
>
> v1:
> - According to dpdk commit 81db321daeccec0c78bbe8bf4492f18f084ba30f,
> remove command "set_hash_input_set <port_id> <flowtype_id> udp-key
> add" to adapt dpdk, contain testplan and testsuite.
>
> *** BLURB HERE ***
>
> Xiang An (2):
> test_plans/dynamic_flowtype: remove a cmd to adapt dpdk
> tests/dynamic_flowtype: remove a cmd to adapt dpdk
>
> test_plans/dynamic_flowtype_test_plan.rst | 48 +++++++++++--------------------
> tests/TestSuite_dynamic_flowtype.py | 2 --
> 2 files changed, 16 insertions(+), 34 deletions(-)
>
Applied the series.
> --
> 1.8.3.1
prev parent reply other threads:[~2021-06-09 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 8:01 Xiang An
2021-06-02 8:01 ` [dts] [PATCH V1 1/2] test_plans/dynamic_flowtype: " Xiang An
2021-06-07 8:53 ` Lin, Xueqin
2021-06-02 8:01 ` [dts] [PATCH V1 2/2] tests/dynamic_flowtype: " Xiang An
2021-06-07 8:53 ` Lin, Xueqin
2021-06-09 7:12 ` 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=8ca6a4dd800445c7a2d09c6c93a4cd23@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=xiangx.an@intel.com \
--cc=xueqin.lin@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).