From: Thomas Monjalon <thomas@monjalon.net>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: Honnappa.Nagarahalli@arm.com, jspewock@iol.unh.edu,
probb@iol.unh.edu, paul.szczepanek@arm.com,
Luca.Vizzarro@arm.com, npratte@iol.unh.edu, dev@dpdk.org,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Luca Vizzarro" <luca.vizzarro@arm.com>
Subject: Re: [PATCH v3] dts: rename execution to test run
Date: Thu, 20 Jun 2024 04:19:59 +0200 [thread overview]
Message-ID: <10233760.OU7Dqq5WaI@thomas> (raw)
In-Reply-To: <20240607083858.58906-1-juraj.linkes@pantheon.tech>
07/06/2024 10:38, Juraj Linkeš:
> The configuration containing the combination of:
> 1. what testbed to use,
> 2. which tests to run,
> 3. and what build targets to test
>
> is called an execution. This is confusing since we're using the exact
> same term to describe other things and execution does not really capture
> that well the three items listed above.
>
> A new term is thus needed to describe the configuration. Test run is
> much less confusing and better captures what the configuration contains.
>
> Depends-on: series-32026 ("dts: update mypy and clean up")
It should be below --- to be ignored by git when applying.
>
> Signed-off-by: Juraj Linkeš <juraj.linkes@pantheon.tech>
> Reviewed-by: Jeremy Spewock <jspewock@iol.unh.edu>
> Reviewed-by: Luca Vizzarro <luca.vizzarro@arm.com>
Applied, thanks.
prev parent reply other threads:[~2024-06-20 2:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 8:51 [PATCH v1] dts: rename execution to test run Juraj Linkeš
2024-04-23 10:58 ` Luca Vizzarro
2024-04-23 12:10 ` Juraj Linkeš
2024-04-30 16:56 ` Jeremy Spewock
2024-05-02 12:05 ` Luca Vizzarro
2024-06-07 8:24 ` [PATCH v2] " Juraj Linkeš
2024-06-07 8:38 ` [PATCH v3] " Juraj Linkeš
2024-06-17 15:02 ` Luca Vizzarro
2024-06-20 2:19 ` Thomas Monjalon [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=10233760.OU7Dqq5WaI@thomas \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Luca.Vizzarro@arm.com \
--cc=dev@dpdk.org \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=npratte@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.