public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Lukas Sismis <sismis@dyna-nic.com>
To: dev@dpdk.org
Cc: stephen@networkplumber.org, Lukas Sismis <sismis@dyna-nic.com>
Subject: [PATCH v6 1/6] cmdline: include stddef.h for MSVC compatibility
Date: Tue, 27 Jan 2026 22:05:26 +0100	[thread overview]
Message-ID: <20260127210532.301464-2-sismis@dyna-nic.com> (raw)
In-Reply-To: <20260127210532.301464-1-sismis@dyna-nic.com>

Include <stddef.h> at the top of cmdline_parse.h before the
fallback offsetof macro definition. This improves MSVC build
compatibility by ensuring the standard offsetof is available
before the fallback definition, avoiding macro redefinition
warnings when building with /WX (warnings as errors).

The standard header provides offsetof on all platforms, and
including it first ensures the fallback is only used when truly
needed.

Signed-off-by: Lukas Sismis <sismis@dyna-nic.com>
---
 lib/cmdline/cmdline_parse.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/lib/cmdline/cmdline_parse.h b/lib/cmdline/cmdline_parse.h
index d9a7d86256..c4131e4af5 100644
--- a/lib/cmdline/cmdline_parse.h
+++ b/lib/cmdline/cmdline_parse.h
@@ -7,6 +7,8 @@
 #ifndef _CMDLINE_PARSE_H_
 #define _CMDLINE_PARSE_H_
 
+#include <stddef.h>
+
 #ifdef __cplusplus
 extern "C" {
 #endif
-- 
2.43.7


  reply	other threads:[~2026-01-27 21:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 21:05 [PATCH v6 0/6] flow_parser: add shared parser library Lukas Sismis
2026-01-27 21:05 ` Lukas Sismis [this message]
2026-01-27 21:05 ` [PATCH v6 2/6] ethdev: add RSS type helper APIs Lukas Sismis
2026-01-27 21:05 ` [PATCH v6 4/6] app/testpmd: use shared flow parser library Lukas Sismis
2026-01-27 21:05 ` [PATCH v6 5/6] examples/flow_parsing: add flow parser demo Lukas Sismis
2026-01-27 21:05 ` [PATCH v6 6/6] test: add flow parser library functional tests Lukas Sismis
2026-01-27 22:18 ` [PATCH v6 0/6] flow_parser: add shared parser library Stephen Hemminger
2026-01-28 18:09 ` 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=20260127210532.301464-2-sismis@dyna-nic.com \
    --to=sismis@dyna-nic.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