From: Alexander Lobakin <aleksander.lobakin@intel.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
nex.sw.ncis.osdt.itp.upstreaming@intel.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/2] net: fix variable shadowing spam from headers
Date: Fri, 29 Mar 2024 17:59:58 +0100 [thread overview]
Message-ID: <20240329170000.3241460-1-aleksander.lobakin@intel.com> (raw)
W=12 and/or C=1 are useful to test new code, but warnings coming from
the generic headers are noisy and distract a lot.
Fix the two most noisy networking header files by using __UNIQUE_ID()
for the variables declared inside macros. The rest seems to be clean,
except for the recent Clang's enum-conversion (which's sanity is still
under discussion).
Alexander Lobakin (2):
net/tcp: fix -Wshadow / Sparse shadow warnings in tcp_hash_fail()
netdev_queues: fix -Wshadow / Sparse shadow warnings throughout the
file
include/net/netdev_queues.h | 54 +++++++++++++++++++++++++++----------
include/net/tcp_ao.h | 6 ++++-
2 files changed, 45 insertions(+), 15 deletions(-)
--
2.44.0
next reply other threads:[~2024-03-29 17:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 16:59 Alexander Lobakin [this message]
2024-03-29 16:59 ` [PATCH net-next 1/2] net/tcp: fix -Wshadow / Sparse shadow warnings in tcp_hash_fail() Alexander Lobakin
2024-03-29 17:00 ` [PATCH net-next 2/2] netdev_queues: fix -Wshadow / Sparse shadow warnings throughout the file Alexander Lobakin
2024-03-29 20:18 ` Jakub Kicinski
2024-03-29 20:18 ` Jakub Kicinski
2024-03-29 20:53 ` Jakub Kicinski
2024-03-29 20:53 ` Jakub Kicinski
2024-04-02 11:53 ` Alexander Lobakin
2024-04-02 12:45 ` Eric Dumazet
2024-04-02 15:53 ` Alexander Lobakin
2024-04-02 16:48 ` Jakub Kicinski
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=20240329170000.3241460-1-aleksander.lobakin@intel.com \
--to=aleksander.lobakin@intel.com \
--cc=0x7f454c46@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®