From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] app/test: fix vdev test in test_eal_flags
Date: Tue, 1 Jul 2014 12:11:20 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8971A797E4D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <53B2A2F8.4060901@6wind.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier MATZ
> Sent: Tuesday, July 01, 2014 1:01 PM
> To: De Lara Guarch, Pablo; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] app/test: fix vdev test in test_eal_flags
>
> Hi Pablo,
>
> On 07/01/2014 01:44 PM, De Lara Guarch, Pablo wrote:
> > Thanks for this. It works fine :)
>
> Thanks for testing!
>
> > Actually, I am thinking of creating a separate test
> > for vdev, out of whitelist test, as it has no relation with it. Do you agree on
> this?
>
> I have no problem with that, it makes sense. Just to confirm: it means
> that Thomas should not apply our previous patches from this thread and
> wait for your next one, right?
That's it :)
>
> Regards,
> Olivier
Thanks,
Pablo
prev parent reply other threads:[~2014-07-01 12:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 14:42 [dpdk-dev] [PATCH] app/test: Removed vdev test in EAL flags unit test Pablo de Lara
2014-07-01 8:31 ` Olivier MATZ
2014-07-01 8:32 ` [dpdk-dev] [PATCH] app/test: fix vdev test in test_eal_flags Olivier Matz
2014-07-01 8:59 ` [dpdk-dev] [PATCH] app/test: Removed vdev test in EAL flags unit test De Lara Guarch, Pablo
2014-07-01 9:20 ` Olivier MATZ
2014-07-01 9:21 ` [dpdk-dev] [PATCH v2] app/test: fix vdev test in test_eal_flags Olivier Matz
2014-07-01 11:44 ` De Lara Guarch, Pablo
2014-07-01 12:00 ` Olivier MATZ
2014-07-01 12:11 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8971A797E4D@IRSMSX103.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).