From: Thomas Monjalon <thomas@monjalon.net>
To: "Trahe, Fiona" <fiona.trahe@intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] devtools: control location of test builds
Date: Thu, 28 Nov 2019 14:20:49 +0100 [thread overview]
Message-ID: <3500673.WMx9tRVn2t@xps> (raw)
In-Reply-To: <BN6PR11MB17963539774AA0996398A9E6E4470@BN6PR11MB1796.namprd11.prod.outlook.com>
28/11/2019 12:47, Trahe, Fiona:
> HI Bruce, Thomas,
> Doesn't the RTE_OUTPUT environment var already resolve this issue?
RTE_OUTPUT is for the build directory, yes.
This patch is about having a top-level directory for all builds
done by the build test scripts.
next prev parent reply other threads:[~2019-11-28 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 10:10 [dpdk-dev] [PATCH] " Bruce Richardson
2019-11-27 23:00 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2019-11-28 9:48 ` Bruce Richardson
2019-11-28 11:47 ` Trahe, Fiona
2019-11-28 13:20 ` Thomas Monjalon [this message]
2019-11-28 18:40 ` David Marchand
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=3500673.WMx9tRVn2t@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=fiona.trahe@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@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).