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, ian.stokes@intel.com,
	konstantin.v.ananyev@yandex.ru, vladimir.medvedkin@intel.com
Subject: [PATCH v2 0/2] fix void function returning a value
Date: Wed, 22 Jan 2025 07:20:42 -0800	[thread overview]
Message-ID: <1737559244-9107-1-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1735254890-18457-3-git-send-email-andremue@linux.microsoft.com>

v2:
 * Updated commit messages to follow standard format.

This patch avoids warnings like the one below emitted by MSVC, and is
needed to get the code to compile cleanly with MSVC.

../drivers/common/idpf/idpf_common_rxtx_avx512.c(139):
    warning C4098: 'idpf_singleq_rearm':
    'void' function returning a value

Andre Muezerie (2):
  drivers/common: fix void function returning a value
  drivers/net: fix void function returning a value

 drivers/common/idpf/idpf_common_rxtx_avx512.c | 12 ++++++++----
 drivers/net/i40e/i40e_rxtx_vec_avx2.c         |  2 +-
 drivers/net/i40e/i40e_rxtx_vec_avx512.c       |  2 +-
 drivers/net/iavf/iavf_rxtx_vec_avx2.c         |  2 +-
 drivers/net/ice/ice_rxtx_vec_avx2.c           |  2 +-
 5 files changed, 12 insertions(+), 8 deletions(-)

--
2.47.2.vfs.0.1


  reply	other threads:[~2025-01-22 15:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 23:14 [PATCH " Andre Muezerie
2024-12-26 23:14 ` [PATCH 1/2] drivers_common: " Andre Muezerie
2024-12-26 23:14 ` [PATCH 2/2] drivers_net: " Andre Muezerie
2025-01-22 15:20   ` Andre Muezerie [this message]
2025-01-22 15:20     ` [PATCH v2 1/2] drivers/common: " Andre Muezerie
2025-01-22 15:47       ` Bruce Richardson
2025-01-22 15:20     ` [PATCH v2 2/2] drivers/net: " Andre Muezerie
2025-01-22 15:48       ` Bruce Richardson

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=1737559244-9107-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=ian.stokes@intel.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --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).