DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andre Muezerie <andremue@linux.microsoft.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: anatoly.burakov@intel.com, bruce.richardson@intel.com,
	dev@dpdk.org, ian.stokes@intel.com, jochen.behrens@broadcom.com,
	vladimir.medvedkin@intel.com
Subject: Re: [PATCH v2] drivers/net: use 64-bit shift and avoid signed/unsigned mismatch
Date: Tue, 14 Jan 2025 13:08:28 -0800	[thread overview]
Message-ID: <20250114210828.GA3357@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <20250114104153.654dec88@hermes.local>

On Tue, Jan 14, 2025 at 10:41:53AM -0800, Stephen Hemminger wrote:
> On Mon,  6 Jan 2025 13:16:55 -0800
> Andre Muezerie <andremue@linux.microsoft.com> wrote:
> 
> > This patch avoids warnings like the ones below emitted by MSVC:
> > 
> > 1)
> > ../drivers/net/ice/base/ice_flg_rd.c(71): warning C4334: '<<':
> >     result of 32-bit shift implicitly converted to 64 bits
> >     (was 64-bit shift intended?)
> > 
> > 2)
> > ../drivers/net/ice/ice_dcf_sched.c(177): warning C4018: '>=':
> >     signed/unsigned mismatch
> > 
> > The fix for (1) is to use 64-bit shifting when appropriate
> > (according to what the result is used for).
> > 
> > The fix for (2) is to explicitly cast the variables used in the
> > comparison.
> > 
> > Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
> > ---
> >  drivers/net/i40e/i40e_ethdev.c       | 22 +++++++++++-----------
> >  drivers/net/iavf/iavf_ethdev.c       |  2 +-
> >  drivers/net/iavf/iavf_rxtx.c         |  2 +-
> >  drivers/net/iavf/iavf_vchnl.c        |  2 +-
> >  drivers/net/ice/base/ice_flg_rd.c    |  4 ++--
> >  drivers/net/ice/base/ice_parser_rt.c | 16 ++++++++--------
> >  drivers/net/ice/base/ice_xlt_kb.c    |  2 +-
> >  drivers/net/ice/base/meson.build     | 19 +++++++++++++------
> 
> Patches to base driver need to be avoided if at all possible.
> Please resubmit without that part

Thanks for the information. I sent out a v3 for this series.
It does contain _coding style issues_ for preexisting code.
Hopefuly that can be ignored.

  reply	other threads:[~2025-01-14 21:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-26 20:59 [PATCH] drivers_net: " Andre Muezerie
2025-01-06 10:54 ` Bruce Richardson
2025-01-06 21:16   ` Andre Muezerie
2025-01-06 21:16 ` [PATCH v2] drivers/net: " Andre Muezerie
2025-01-14 18:41   ` Stephen Hemminger
2025-01-14 21:08     ` Andre Muezerie [this message]
2025-01-14 23:30       ` Stephen Hemminger
2025-01-14 21:05 ` [PATCH v3] " 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=20250114210828.GA3357@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --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=jochen.behrens@broadcom.com \
    --cc=stephen@networkplumber.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).