From: Stephen Hemminger <stephen@networkplumber.org>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, david.marchand@redhat.com, dmitry.kozliuk@gmail.com
Subject: Re: [PATCH 2/2] test: enable lcores test on Windows
Date: Wed, 14 Dec 2022 08:53:32 -0800 [thread overview]
Message-ID: <20221214085332.2a48db79@hermes.local> (raw)
In-Reply-To: <1670287169-15325-3-git-send-email-roretzla@linux.microsoft.com>
On Mon, 5 Dec 2022 16:39:29 -0800
Tyler Retzlaff <roretzla@linux.microsoft.com> wrote:
> Stop using pthread and convert the test to use EAL thread APIs. Because
> the EAL thread APIs provide more than just a stub for thread join on
> Windows the tests now pass and need not be skipped.
>
> Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
This makes sense to cover the API's even if not on Windows.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2022-12-14 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 0:39 [PATCH 0/2] " Tyler Retzlaff
2022-12-06 0:39 ` [PATCH 1/2] eal: add missing call marking memory config complete Tyler Retzlaff
2022-12-14 16:52 ` Stephen Hemminger
2022-12-15 9:59 ` David Marchand
2022-12-15 18:07 ` Tyler Retzlaff
2022-12-06 0:39 ` [PATCH 2/2] test: enable lcores test on Windows Tyler Retzlaff
2022-12-14 16:53 ` Stephen Hemminger [this message]
2022-12-12 20:36 ` [PATCH 0/2] " Tyler Retzlaff
2022-12-16 17:16 ` [PATCH v2 0/2] Enable the lcores test on Windows instead of skipping it Tyler Retzlaff
2022-12-16 17:16 ` [PATCH v2 1/2] eal: add missing call marking memory config complete Tyler Retzlaff
2022-12-16 17:16 ` [PATCH v2 2/2] test: enable lcores test on Windows Tyler Retzlaff
2022-12-21 15:03 ` [PATCH v2 0/2] Enable the lcores test on Windows instead of skipping it 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=20221214085332.2a48db79@hermes.local \
--to=stephen@networkplumber.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=roretzla@linux.microsoft.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).