DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dev <dev@dpdk.org>,
	 "Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>
Cc: Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	 Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4 0/5] no-huge unit test
Date: Tue, 24 Mar 2020 11:06:20 +0100	[thread overview]
Message-ID: <CAJFAV8w_V9=db7RmSydyfi-bMfuXzyP3bkp=kc7xhvT1oMXxmw@mail.gmail.com> (raw)
In-Reply-To: <20200323195926.12182-1-david.marchand@redhat.com>

On Mon, Mar 23, 2020 at 8:59 PM David Marchand
<david.marchand@redhat.com> wrote:
>
> This is a respin of Ruifeng series with a patch I sent earlier today.
>
> Changelog since v3:
> - patch 1 is new,
> - patch 3 is the only that has differences,

Series applied, thanks Ruifeng.

Small note, in containers all cores from the travis arm systems are
seen, so unit tests will run against more cores than in x86_64 virtual
machines.


-- 
David Marchand


      parent reply	other threads:[~2020-03-24 10:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 19:59 David Marchand
2020-03-23 19:59 ` [dpdk-dev] [PATCH v4 1/5] test: load drivers when required David Marchand
2020-03-23 21:01   ` Aaron Conole
2020-03-23 19:59 ` [dpdk-dev] [PATCH v4 2/5] test: skip subtests in no-huge mode David Marchand
2020-03-23 19:59 ` [dpdk-dev] [PATCH v4 3/5] test: allow no-huge mode for fast-tests David Marchand
2020-03-23 19:59 ` [dpdk-dev] [PATCH v4 4/5] ci: run tests even without hugepage David Marchand
2020-03-23 19:59 ` [dpdk-dev] [PATCH v4 5/5] ci: enable unit test for aarch64 David Marchand
2020-03-24 10:06 ` David Marchand [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='CAJFAV8w_V9=db7RmSydyfi-bMfuXzyP3bkp=kc7xhvT1oMXxmw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=maicolgabriel@hotmail.com \
    --cc=ruifeng.wang@arm.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).