From: "Huang, ZhiminX" <zhiminx.huang@intel.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiale, SongX" <songx.jiale@intel.com>
Subject: Re: [dts] [PATCH V2 1/2] test_plans/cvl_dcf_flow_priority: modify rule priority
Date: Wed, 20 Oct 2021 09:47:31 +0000 [thread overview]
Message-ID: <BN0PR11MB57122F93D808CCBFA2025E66FDBE9@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <5d3bca81a4574c1ab73c4c512c426613@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Tu, Lijuan
> Sent: Monday, September 27, 2021 2:32 PM
> To: Jiale, SongX <songx.jiale@intel.com>; dts@dpdk.org
> Cc: Jiale, SongX <songx.jiale@intel.com>
> Subject: Re: [dts] [PATCH V2 1/2] test_plans/cvl_dcf_flow_priority: modify rule
> priority
>
> > -----Original Message-----
> > From: dts <dts-bounces@dpdk.org> On Behalf Of Jiale Song
> > Sent: 2021年9月15日 13:40
> > To: dts@dpdk.org
> > Cc: Jiale, SongX <songx.jiale@intel.com>
> > Subject: [dts] [PATCH V2 1/2] test_plans/cvl_dcf_flow_priority: modify
> > rule priority
> >
> > because the priority of the dpdk rule is changed from 0<1<2... to
> > 0>1>2..., modify the testplan
> >
> > Signed-off-by: Jiale Song <songx.jiale@intel.com>
>
> Could you please provide me dpdk commit ?
According to dpdk commit 72908beba944b57e3e1cbe0edf7728a192230d2b, modified testplan.
prev parent reply other threads:[~2021-10-20 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 5:39 Jiale Song
2021-09-15 5:39 ` [dts] [PATCH V2 2/2] tests/cvl_dcf_flow_priority: modify the script according to the testplan Jiale Song
2021-10-22 9:22 ` Tu, Lijuan
2021-09-27 6:31 ` [dts] [PATCH V2 1/2] test_plans/cvl_dcf_flow_priority: modify rule priority Tu, Lijuan
2021-10-20 9:47 ` Huang, ZhiminX [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=BN0PR11MB57122F93D808CCBFA2025E66FDBE9@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=zhiminx.huang@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
--cc=songx.jiale@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).