DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: bruce.richardson@intel.com
Cc: anatoly.burakov@intel.com,
	Andre Muezerie <andremue@linux.microsoft.com>,
	dev@dpdk.org, ian.stokes@intel.com,
	konstantin.v.ananyev@yandex.ru,  vladimir.medvedkin@intel.com
Subject: Re: [PATCH v2 0/2] fix void function returning a value
Date: Thu, 23 Jan 2025 13:23:15 +0100	[thread overview]
Message-ID: <CAJFAV8yNg8jtpubkRfLwCtG1pKY+mzztg-AsvRpNVT2w8CB7fA@mail.gmail.com> (raw)
In-Reply-To: <1737559244-9107-1-git-send-email-andremue@linux.microsoft.com>

Hello Bruce,

On Wed, Jan 22, 2025 at 4:21 PM Andre Muezerie
<andremue@linux.microsoft.com> wrote:
>
> 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(-)

I see the series is delegated to the main repo (Thomas).

This touches only Intel drivers and the code deduplication effort you
started may conflict (though trivially) with such changes depending on
when it lands.

Would you mind merging this fixes from Andre through the
next-net-intel tree, right now?
If so, please mark it as delegated to you in patchwork.


Thanks!

-- 
David Marchand


  parent reply	other threads:[~2025-01-23 12:23 UTC|newest]

Thread overview: 12+ 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   ` [PATCH v2 0/2] " Andre Muezerie
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
2025-01-23 12:23     ` David Marchand [this message]
2025-01-23 12:46       ` [PATCH v2 0/2] " Bruce Richardson
2025-01-23 13:03         ` David Marchand
2025-01-23 14:08           ` 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=CAJFAV8yNg8jtpubkRfLwCtG1pKY+mzztg-AsvRpNVT2w8CB7fA@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=andremue@linux.microsoft.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).