DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andre Muezerie <andremue@linux.microsoft.com>
To: andremue@linux.microsoft.com
Cc: anatoly.burakov@intel.com, bruce.richardson@intel.com,
	dev@dpdk.org, dsinghrawat@marvell.com, palok@marvell.com,
	stephen@networkplumber.org
Subject: [PATCH v2 0/2] remove unused variables and add MSVC compiler flag
Date: Tue, 14 Jan 2025 12:46:49 -0800	[thread overview]
Message-ID: <1736887611-32186-1-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1735238504-15597-3-git-send-email-andremue@linux.microsoft.com>

Removed unused variables and added MSVC specific compiler flag to
ignore warnings about unused variables, like is being done for
other compilers.

Andre Muezerie (2):
  drivers/common: remove unused variables and add MSVC compiler flag
  drivers/net: add MSVC compiler flag for unused variables

 drivers/common/idpf/base/meson.build       | 13 +++--
 drivers/common/idpf/idpf_common_rxtx.c     |  2 -
 drivers/common/idpf/idpf_common_virtchnl.c |  4 +-
 drivers/common/sfc_efx/base/efx_mae.c      |  2 +-
 drivers/common/sfc_efx/base/efx_table.c    |  1 -
 drivers/common/sfc_efx/base/meson.build    | 20 +++++---
 drivers/net/ice/base/meson.build           | 16 ++++--
 drivers/net/qede/base/meson.build          | 57 ++++++++++++----------
 8 files changed, 69 insertions(+), 46 deletions(-)

--
2.47.0.vfs.0.3


  parent reply	other threads:[~2025-01-14 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 18:41 [PATCH " Andre Muezerie
2024-12-26 18:41 ` [PATCH 1/2] drivers/common: " Andre Muezerie
2025-01-06 10:50   ` Bruce Richardson
2024-12-26 18:41 ` [PATCH 2/2] drivers/net: " Andre Muezerie
2025-01-14 17:46   ` Stephen Hemminger
2025-01-14 20:46   ` Andre Muezerie [this message]
2025-01-14 20:46     ` [PATCH v2 1/2] drivers/common: " Andre Muezerie
2025-01-14 20:46     ` [PATCH v2 2/2] drivers/net: add MSVC compiler flag for unused variables 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=1736887611-32186-1-git-send-email-andremue@linux.microsoft.com \
    --to=andremue@linux.microsoft.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dsinghrawat@marvell.com \
    --cc=palok@marvell.com \
    --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;
as well as URLs for NNTP newsgroup(s).