From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, <dev@dpdk.org>
Subject: Re: [PATCH v4 4/8] test: use unit test runner for eal flags
Date: Fri, 21 Nov 2025 13:06:03 +0100 [thread overview]
Message-ID: <21dbee1a-bde4-4682-9f46-e41498a9c1e3@intel.com> (raw)
In-Reply-To: <20251120165713.120238-5-stephen@networkplumber.org>
On 11/20/2025 5:55 PM, Stephen Hemminger wrote:
> Make the sub tests in eal flags suite into a group
> so that they are not individual tests.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2025-11-21 12:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0251115193409.99740-1-stephen@networkplumber.org>
2025-11-20 16:55 ` [PATCH v4 0/8] tests: enable format truncation checks Stephen Hemminger
2025-11-20 16:55 ` [PATCH v4 1/8] test: increase size of memzone name Stephen Hemminger
2025-11-20 16:55 ` [PATCH v4 2/8] test: refactor file prefix arg handling Stephen Hemminger
2025-11-20 16:55 ` [PATCH v4 3/8] test: avoid overflowing huge directory path Stephen Hemminger
2025-11-21 12:04 ` Burakov, Anatoly
2025-11-20 16:55 ` [PATCH v4 4/8] test: use unit test runner for eal flags Stephen Hemminger
2025-11-21 12:06 ` Burakov, Anatoly [this message]
2025-11-20 16:55 ` [PATCH v4 5/8] test: fix format overflow warning in ACL test Stephen Hemminger
2025-11-21 12:06 ` Burakov, Anatoly
2025-11-20 16:55 ` [PATCH v4 6/8] test: fix impossible format-truncation in cfgfiles Stephen Hemminger
2025-11-21 12:09 ` Burakov, Anatoly
2025-11-20 16:55 ` [PATCH v4 7/8] test: fix format overflow in cryptodev test Stephen Hemminger
2025-11-21 12:08 ` Burakov, Anatoly
2025-11-20 16:55 ` [PATCH v4 8/8] test: re-enable format-truncation warnings Stephen Hemminger
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=21dbee1a-bde4-4682-9f46-e41498a9c1e3@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).