DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: dev@dpdk.org, vladimir.medvedkin@intel.com
Subject: [PATCH v5 0/2] enable fib to be compiled with MSVC
Date: Fri, 16 May 2025 13:45:33 -0700	[thread overview]
Message-ID: <1747428335-3736-1-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1733281010-23780-1-git-send-email-andremue@linux.microsoft.com>

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.

v5:
- enabled fib to be compiled with MSVC

Andre Muezerie (2):
  lib/fib: remove warning about implicit 64-bit conversion
  lib/fib: enable fib to be compiled with MSVC

 lib/fib/meson.build | 6 ------
 lib/fib/trie.c      | 2 +-
 2 files changed, 1 insertion(+), 7 deletions(-)

--
2.49.0.vfs.0.3


  parent reply	other threads:[~2025-05-16 20:45 UTC|newest]

Thread overview: 13+ 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 ` Andre Muezerie [this message]
2025-05-16 20:45   ` [PATCH v5 1/2] " Andre Muezerie
2025-05-16 20:45   ` [PATCH v5 2/2] lib/fib: enable fib to be compiled with MSVC Andre Muezerie

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=1747428335-3736-1-git-send-email-andremue@linux.microsoft.com \
    --to=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).