From: "Sun, QinX" <qinx.sun@intel.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/iavf_fdir: reload driver to reduce the interaction between cases
Date: Wed, 2 Jun 2021 10:20:21 +0000 [thread overview]
Message-ID: <SJ0PR11MB48634861482B08C0AADF3DB1873D9@SJ0PR11MB4863.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210602104156.30955-1-qinx.sun@intel.com>
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
> -----Original Message-----
> From: Sun, QinX <qinx.sun@intel.com>
> Sent: Wednesday, June 2, 2021 6:42 PM
> To: dts@dpdk.org
> Cc: Sun, QinX <qinx.sun@intel.com>
> Subject: [dts] [PATCH V1] tests/iavf_fdir: reload driver to reduce the interaction between cases
Tested-by: Qin Sun <qinx.sun@intel.com>
[-- Attachment #2: TestIAVFFdir.log --]
[-- Type: application/octet-stream, Size: 1957668 bytes --]
next prev parent reply other threads:[~2021-06-02 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 10:41 Qin Sun
2021-06-02 10:20 ` Sun, QinX [this message]
2021-06-09 7:16 ` Tu, Lijuan
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=SJ0PR11MB48634861482B08C0AADF3DB1873D9@SJ0PR11MB4863.namprd11.prod.outlook.com \
--to=qinx.sun@intel.com \
--cc=dts@dpdk.org \
/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).