From: Stephen Hemminger <stephen@networkplumber.org>
To: Andre Muezerie <andremue@linux.microsoft.com>
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 15:30:54 -0800 [thread overview]
Message-ID: <20250114153054.01906f7e@hermes.local> (raw)
In-Reply-To: <20250114210828.GA3357@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Tue, 14 Jan 2025 13:08:28 -0800
Andre Muezerie <andremue@linux.microsoft.com> wrote:
> >
> > 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.
Yeah, that is common. I always look to see why checkpatch is whining
before merging.
next prev parent reply other threads:[~2025-01-14 23:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 20:59 [PATCH] drivers_net: use 64-bit shift and avoid signed/unsigned mismatch 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
2025-01-14 23:30 ` Stephen Hemminger [this message]
2025-01-14 21:05 ` [PATCH v3] " Andre Muezerie
2025-02-05 18:35 ` Stephen Hemminger
2025-02-05 19:38 ` Andre Muezerie
2025-02-05 19:32 ` [PATCH v4] " Andre Muezerie
2025-02-06 11:07 ` Bruce Richardson
2025-02-07 15:46 ` Andre Muezerie
2025-02-07 15:56 ` Bruce Richardson
2025-02-07 17:47 ` Andre Muezerie
2025-02-07 17:56 ` Stephen Hemminger
2025-02-07 17:41 ` [PATCH v5 0/1] use 64-bit shift, " Andre Muezerie
2025-02-07 17:41 ` [PATCH v5 1/1] drivers/net: use 64-bit shift and " Andre Muezerie
2025-02-07 19:00 ` [PATCH v5 0/1] use 64-bit shift, " Stephen Hemminger
2025-02-07 19:01 ` Stephen Hemminger
2025-02-10 9:35 ` Bruce Richardson
2025-02-10 16:07 ` Bruce Richardson
2025-02-10 20:32 ` Andre Muezerie
2025-02-10 21:02 ` 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=20250114153054.01906f7e@hermes.local \
--to=stephen@networkplumber.org \
--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=jochen.behrens@broadcom.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.