From: David Marchand <david.marchand@redhat.com>
To: Andre Muezerie <andremue@linux.microsoft.com>
Cc: dev@dpdk.org, vladimir.medvedkin@intel.com
Subject: Re: [PATCH v5 0/2] enable fib to be compiled with MSVC
Date: Tue, 3 Jun 2025 16:33:16 +0200 [thread overview]
Message-ID: <CAJFAV8xc+WjtM6Zwu5OPLxbsiBXTshxxWeSaLv75=7-4AGnFEw@mail.gmail.com> (raw)
In-Reply-To: <1747428335-3736-1-git-send-email-andremue@linux.microsoft.com>
On Fri, May 16, 2025 at 10:46 PM Andre Muezerie
<andremue@linux.microsoft.com> wrote:
>
> This patchset addresses the issues in lib/fib that were preventing
> compilation with MSVC. The first patch removes a warning about
> implicit 64-bit conversion, and the second patch enables the
> compilation of fib with MSVC.
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2025-06-03 14:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 2:56 [PATCH] lib/fib: remove warning about implicit 64-bit conversion Andre Muezerie
2024-12-04 22:59 ` Stephen Hemminger
2024-12-05 15:34 ` Andre Muezerie
2024-12-05 15:38 ` [PATCH v2] " Andre Muezerie
2025-03-03 22:54 ` [PATCH v3] " Andre Muezerie
2025-03-04 6:49 ` Stephen Hemminger
2025-03-04 16:51 ` Andre Muezerie
2025-03-04 10:47 ` Bruce Richardson
2025-03-04 16:52 ` Andre Muezerie
2025-03-04 16:48 ` [PATCH v4] " Andre Muezerie
2025-05-16 20:45 ` [PATCH v5 0/2] enable fib to be compiled with MSVC Andre Muezerie
2025-05-16 20:45 ` [PATCH v5 1/2] lib/fib: remove warning about implicit 64-bit conversion Andre Muezerie
2025-05-17 10:07 ` Morten Brørup
2025-05-17 11:09 ` Stephen Hemminger
2025-05-17 12:59 ` Morten Brørup
2025-05-16 20:45 ` [PATCH v5 2/2] lib/fib: enable fib to be compiled with MSVC Andre Muezerie
2025-06-03 14:33 ` David Marchand [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='CAJFAV8xc+WjtM6Zwu5OPLxbsiBXTshxxWeSaLv75=7-4AGnFEw@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=vladimir.medvedkin@intel.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).