From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Dong, JunX" <junx.dong@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1 6/6] tests/*: update test suits after removed fm10k
Date: Fri, 18 Jun 2021 06:51:06 +0000 [thread overview]
Message-ID: <141eee8d36b14b6a9c792bbc4f1b22fd@intel.com> (raw)
In-Reply-To: <BN9PR11MB5274CA2BE703D61510E11755EA0F9@BN9PR11MB5274.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Dong, JunX <junx.dong@intel.com>
> Sent: 2021年6月16日 11:31
> To: dts@dpdk.org
> Cc: Tu, Lijuan <lijuan.tu@intel.com>
> Subject: RE: [dts][PATCH V1 6/6] tests/*: update test suits after removed fm10k
>
>
>
> -----Original Message-----
> From: Dong, JunX <junx.dong@intel.com>
> Sent: Tuesday, June 15, 2021 6:46 PM
> To: Dong, JunX <junx.dong@intel.com>
> Cc: dts@dpdk.org
> Subject: [dts][PATCH V1 6/6] tests/*: update test suits after removed fm10k
> Signed-off-by: Jun Dong <junx.dong@intel.com>
>
>
> Tested-by: Jun Dong <junx.dong@intel.com>
Applied the series, thanks
prev parent reply other threads:[~2021-06-18 6:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 10:46 [dts] [PATCH V1 1/6] dts/*: remove fm10k related modules and patch Jun Dong
2021-06-15 10:46 ` [dts] [PATCH V1 2/6] conf/test_case_checklist: update test case checklist after removed fm10k Jun Dong
2021-06-15 10:46 ` [dts] [PATCH V1 3/6] framework/*: update framework " Jun Dong
2021-06-15 10:46 ` [dts] [PATCH V1 4/6] nics/net_device: update NetDevice class " Jun Dong
2021-06-15 10:46 ` [dts] [PATCH V1 5/6] test_plans/*: update test plan " Jun Dong
2021-06-15 10:46 ` [dts] [PATCH V1 6/6] tests/*: update test suits " Jun Dong
[not found] ` <BN9PR11MB527491B1E7491772751169B7EA0F9@BN9PR11MB5274.namprd11.prod.outlook.com>
[not found] ` <BN9PR11MB5274CA2BE703D61510E11755EA0F9@BN9PR11MB5274.namprd11.prod.outlook.com>
2021-06-18 6:51 ` 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=141eee8d36b14b6a9c792bbc4f1b22fd@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=junx.dong@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).