From: Patrick Robb <probb@iol.unh.edu>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, david.marchand@redhat.com
Subject: Re: [PATCH v3 2/2] stack: enable build with MSVC
Date: Tue, 4 Feb 2025 12:42:04 -0500 [thread overview]
Message-ID: <CAJvnSUCPs17GEFBpOuJEnSLLh3exj_iTUNxOxBTjNmMpfbdyuA@mail.gmail.com> (raw)
In-Reply-To: <1738634318-12876-3-git-send-email-andremue@linux.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 101 bytes --]
Recheck-request: iol-intel-Performance
Triggering a retest in CI for the failed performance result.
[-- Attachment #2: Type: text/html, Size: 508 bytes --]
prev parent reply other threads:[~2025-02-04 17:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 16:32 [PATCH 0/3] enable build of lib/stack when using MSVC Andre Muezerie
2024-12-10 16:32 ` [PATCH 1/3] lib/eal: add rte_atomic128_cmp_exchange compatible with MSVC Andre Muezerie
2025-01-24 14:27 ` David Marchand
2025-01-28 21:25 ` Andre Muezerie
2024-12-10 16:32 ` [PATCH 2/3] app/test: add basic test for rte_atomic128_cmp_exchange Andre Muezerie
2024-12-10 16:32 ` [PATCH 3/3] lib/stack: enable build with MSVC Andre Muezerie
2025-01-28 21:16 ` [PATCH v2 0/2] enable build of lib/stack when using MSVC Andre Muezerie
2025-01-28 21:16 ` [PATCH v2 1/2] test: disable non-C11 atomic tests for MSVC Andre Muezerie
2025-01-28 21:16 ` [PATCH v2 2/2] stack: enable build with MSVC Andre Muezerie
2025-02-04 1:58 ` [PATCH v3 0/2] enable build of lib/stack when using MSVC Andre Muezerie
2025-02-04 1:58 ` [PATCH v3 1/2] test: disable non-C11 atomic tests for MSVC Andre Muezerie
2025-02-04 1:58 ` [PATCH v3 2/2] stack: enable build with MSVC Andre Muezerie
2025-02-04 10:30 ` Bruce Richardson
2025-02-04 15:25 ` Andre Muezerie
2025-02-04 17:42 ` Patrick Robb [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=CAJvnSUCPs17GEFBpOuJEnSLLh3exj_iTUNxOxBTjNmMpfbdyuA@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=andremue@linux.microsoft.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.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).