DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dean Marx <dmarx@iol.unh.edu>
To: Luca Vizzarro <luca.vizzarro@arm.com>
Cc: dev@dpdk.org, "Paul Szczepanek" <paul.szczepanek@arm.com>,
	"Patrick Robb" <probb@iol.unh.edu>,
	"Tomáš Ďurovec" <tomas.durovec@pantheon.tech>
Subject: Re: [PATCH v2 5/7] dts: add support for externally compiled DPDK
Date: Fri, 25 Oct 2024 14:29:24 -0400	[thread overview]
Message-ID: <CABD7UXOmGgg8KxpTmJJF3WBgV0X7KzVqojrijK-netFuCnR00Q@mail.gmail.com> (raw)
In-Reply-To: <20241021134935.1210500-6-luca.vizzarro@arm.com>

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

Just wondering, if the user wants to run DTS using the configuration yaml
file or the environment variables instead of the command line args, are
they supposed to run main.py by itself after setup? Because right now, it
won't run without the --tarball or --dpdk-tree args, even if it's specified
in the config file. It seems like it just ignores whatever was specified in
the command line if it's specified in the yaml file, but won't execute
without the command line args either.

[-- Attachment #2: Type: text/html, Size: 545 bytes --]

  reply	other threads:[~2024-10-25 18:29 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 16:01 [PATCH 0/7] DTS external DPDK build Tomáš Ďurovec
2024-09-30 16:01 ` [PATCH 1/7] dts: rename build target to " Tomáš Ďurovec
2024-09-30 16:01 ` [PATCH 2/7] dts: one dpdk build per test run Tomáš Ďurovec
2024-09-30 16:02 ` [PATCH 3/7] dts: fix remote session file transfer vars Tomáš Ďurovec
2024-09-30 16:02 ` [PATCH 4/7] dts: add the ability to copy directories via remote Tomáš Ďurovec
2024-09-30 16:02 ` [PATCH 5/7] dts: add support for externally compiled DPDK Tomáš Ďurovec
2024-09-30 16:02 ` [PATCH 6/7] doc: update argument options for external DPDK build Tomáš Ďurovec
2024-09-30 16:02 ` [PATCH 7/7] dts: remove git ref option Tomáš Ďurovec
2024-10-21 13:49 ` [PATCH v2 0/7] DTS external DPDK build Luca Vizzarro
2024-10-21 13:49   ` [PATCH v2 1/7] dts: rename build target to " Luca Vizzarro
2024-10-25 18:05     ` Dean Marx
2024-10-21 13:49   ` [PATCH v2 2/7] dts: enforce one dpdk build per test run Luca Vizzarro
2024-10-25 18:08     ` Dean Marx
2024-10-21 13:49   ` [PATCH v2 3/7] dts: fix remote session file transfer vars Luca Vizzarro
2024-10-21 13:49   ` [PATCH v2 4/7] dts: enable copying directories to and from nodes Luca Vizzarro
2024-10-25 18:12     ` Dean Marx
2024-10-21 13:49   ` [PATCH v2 5/7] dts: add support for externally compiled DPDK Luca Vizzarro
2024-10-25 18:29     ` Dean Marx [this message]
2024-10-21 13:49   ` [PATCH v2 6/7] doc: update argument options for external DPDK build Luca Vizzarro
2024-10-25 18:30     ` Dean Marx
2024-10-21 13:49   ` [PATCH v2 7/7] dts: remove git ref option Luca Vizzarro
2024-10-25 18:31     ` Dean Marx
2024-10-21 22:39   ` [PATCH v2 0/7] DTS external DPDK build Dean Marx
2024-10-22  7:27     ` Paul Szczepanek
2024-10-22 14:56     ` Luca Vizzarro
2024-10-24 17:14       ` Dean Marx
2024-10-21 22:46 ` [PATCH v3 " Luca Vizzarro
2024-10-21 22:46   ` [PATCH v3 1/7] dts: rename build target to " Luca Vizzarro
2024-10-21 22:46   ` [PATCH v3 2/7] dts: enforce one dpdk build per test run Luca Vizzarro
2024-10-21 22:46   ` [PATCH v3 3/7] dts: change remote and local paths objects Luca Vizzarro
2024-10-25 18:10     ` Dean Marx
2024-10-21 22:46   ` [PATCH v3 4/7] dts: enable copying directories to and from nodes Luca Vizzarro
2024-10-21 22:46   ` [PATCH v3 5/7] dts: add support for externally compiled DPDK Luca Vizzarro
2024-10-21 22:46   ` [PATCH v3 6/7] doc: update argument options for external DPDK build Luca Vizzarro
2024-10-21 22:46   ` [PATCH v3 7/7] dts: remove git ref option Luca Vizzarro

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=CABD7UXOmGgg8KxpTmJJF3WBgV0X7KzVqojrijK-netFuCnR00Q@mail.gmail.com \
    --to=dmarx@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=luca.vizzarro@arm.com \
    --cc=paul.szczepanek@arm.com \
    --cc=probb@iol.unh.edu \
    --cc=tomas.durovec@pantheon.tech \
    /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).