From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Dean Marx <dmarx@iol.unh.edu>
Cc: dev@dpdk.org, Paul Szczepanek <paul.szczepanek@arm.com>,
Patrick Robb <probb@iol.unh.edu>
Subject: Re: [PATCH 3/6] dts: add tmp directory facility
Date: Tue, 11 Mar 2025 13:35:46 +0200 [thread overview]
Message-ID: <6fb3ef90-4af1-4c2d-acb3-97a4777cda58@arm.com> (raw)
In-Reply-To: <CABD7UXNmGggR7MMysLVcyF=80WzOaee-eDcenVgFNoThrdPa4A@mail.gmail.com>
On 05/03/2025 23:29, Dean Marx wrote:
> This makes sense, I noticed though that nothing is actually stored in
> these placeholder directories yet, and dpdk is built in a separate
> folder. Is the plan in the future to move this to the placeholder
> directory? Or is there a different use case?
>
> Reviewed-by: Dean Marx <dmarx@iol.unh.edu>
This is used in this patch series in `dts: enable build-less DPDK driver
binding`. But yes the plan is to move everything to use a dedicated tmp
folder. We don't want stray files/folders.
next prev parent reply other threads:[~2025-03-11 11:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 13:28 [PATCH 0/6] dts: add build-less driver binding Luca Vizzarro
2025-02-24 13:28 ` [PATCH 1/6] dts: ensure runtime working directory Luca Vizzarro
2025-03-05 21:24 ` Dean Marx
2025-02-24 13:28 ` [PATCH 2/6] dts: use topology in smoke tests Luca Vizzarro
2025-03-05 21:26 ` Dean Marx
2025-03-11 11:33 ` Luca Vizzarro
2025-02-24 13:28 ` [PATCH 3/6] dts: add tmp directory facility Luca Vizzarro
2025-03-05 21:29 ` Dean Marx
2025-03-05 21:34 ` Dean Marx
2025-03-11 11:35 ` Luca Vizzarro [this message]
2025-02-24 13:28 ` [PATCH 4/6] dts: decouple DPDK runtime from build Luca Vizzarro
2025-03-05 21:30 ` Dean Marx
2025-02-24 13:28 ` [PATCH 5/6] dts: enable build-less DPDK driver binding Luca Vizzarro
2025-03-05 21:33 ` Dean Marx
2025-02-24 13:28 ` [PATCH 6/6] dts: restore TG setup and teardown Luca Vizzarro
2025-03-05 21:36 ` Dean Marx
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=6fb3ef90-4af1-4c2d-acb3-97a4777cda58@arm.com \
--to=luca.vizzarro@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
/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).