From: "Liu, Yong" <yong.liu@intel.com>
To: "Xu, HuilongX" <huilongx.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [dts 2/4] [PATCH V1] add generic_filter test for fortville NIC
Date: Tue, 26 May 2015 01:29:38 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10E3388A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <DF2A19295B96364286FEB7F3DDA27A4601112A62@SHSMSX101.ccr.corp.intel.com>
Agree with you.
> -----Original Message-----
> From: Xu, HuilongX
> Sent: Monday, May 25, 2015 5:16 PM
> To: Liu, Yong; dts@dpdk.org
> Subject: RE: [dts] [dts 2/4] [PATCH V1] add generic_filter test for
> fortville NIC
>
> Hi yong,
> Yes, this is a good suggest.
> I will great a folder, and move the FVL execution file to it at next patch.
> Would you agree?
>
> > -----Original Message-----
> > From: Liu, Yong
> > Sent: Monday, May 25, 2015 4:59 PM
> > To: Xu, HuilongX; dts@dpdk.org
> > Subject: RE: [dts] [dts 2/4] [PATCH V1] add generic_filter test for
> > fortville NIC
> >
> > Huilong,
> >
> > You can make specified folder named "executions" to save different types
> > of execution files.
> > There will be several different kinds execution files, it will left
> chaos
> > if we put all files in dts root folder.
> >
> > > -----Original Message-----
> > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of huilong,xu
> > > Sent: Monday, May 25, 2015 4:54 PM
> > > To: dts@dpdk.org
> > > Subject: [dts] [dts 2/4] [PATCH V1] add generic_filter test for
> > fortville
> > > NIC
> > >
> > > From: huilong xu <huilongx.xu@intel.com>
> > >
> > >
> > > Signed-off-by: huilong xu <huilongx.xu@intel.com>
> > > ---
> > > execution_FVL.cfg | 3 ++-
> > > 1 files changed, 2 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/execution_FVL.cfg b/execution_FVL.cfg
> > > index c57f33d..7e5151b 100644
> > > --- a/execution_FVL.cfg
> > > +++ b/execution_FVL.cfg
> > > @@ -3,7 +3,8 @@ crbs=<CRB IP Address>
> > > drivername=<driver name igb_uio or vfio-pci>
> > > test_suites=
> > > checksum_offload,
> > > - dynamic_config
> > > + dynamic_config,
> > > + generic_filter
> > > targets=
> > > x86_64-native-linuxapp-gcc
> > > parameters=nic_type=cfg:func=true
> > > --
> > > 1.7.4.4
next prev parent reply other threads:[~2015-05-26 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 8:54 [dts] [dts 1/4] [PATCH V1] add generic_filter test for niantic NIC huilong,xu
2015-05-25 8:54 ` [dts] [dts 2/4] [PATCH V1] add generic_filter test for fortville NIC huilong,xu
2015-05-25 8:59 ` Liu, Yong
2015-05-25 9:15 ` Xu, HuilongX
2015-05-26 1:29 ` Liu, Yong [this message]
2015-05-25 8:54 ` [dts] [dts 3/4] [PATCH V1] add generic_filter test plan huilong,xu
2015-05-26 2:11 ` Liu, Yong
2015-05-26 5:33 ` Xu, HuilongX
2015-05-25 8:54 ` [dts] [dts 4/4] [PATCH V1] add generic filter huilong,xu
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=86228AFD5BCD8E4EBFD2B90117B5E81E10E3388A@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=huilongx.xu@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).