From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Skorodumov <skorodumov.dmitry@huawei.com>
Cc: <netdev@vger.kernel.org>, Julian Vetter <julian@outer-limits.org>,
Ido Schimmel <idosch@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Guillaume Nault <gnault@redhat.com>,
Mahesh Bandewar <maheshb@google.com>,
"David S. Miller" <davem@davemloft.net>,
<linux-kernel@vger.kernel.org>, <andrey.bokhanko@huawei.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH v2 net-next] ipvlan: Fix sparse warning about __be32 -> u32
Date: Thu, 20 Nov 2025 09:42:15 -0800 [thread overview]
Message-ID: <20251120094215.3e156548@kernel.org> (raw)
In-Reply-To: <20251120172636.3818116-1-skorodumov.dmitry@huawei.com>
On Thu, 20 Nov 2025 20:26:32 +0300 Dmitry Skorodumov wrote:
> Fixed a sparse warning:
>
> ipvlan_core.c:56: warning: incorrect type in argument 1
> (different base types) expected unsigned int [usertype] a
> got restricted __be32 const [usertype] s_addr
>
> Force cast the s_addr to u32
>
> Fixes: 2ad7bf363841 ("ipvlan: Initial check-in of the IPVLAN driver.")
> Signed-off-by: Dmitry Skorodumov <skorodumov.dmitry@huawei.com>
Read this please:
https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
v1 was fine, why are you adding a Fixes tag in a non-functional change
:| I can't dig out v1 now because k.org aggressively supersedes the
patches. Send a v3 *while following the rules*.
--
pw-bot: cr
prev parent reply other threads:[~2025-11-20 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 17:26 [PATCH v2 net-next] ipvlan: Fix sparse warning about __be32 -> u32 Dmitry Skorodumov
2025-11-20 17:42 ` Jakub Kicinski [this message]
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=20251120094215.3e156548@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrey.bokhanko@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gnault@redhat.com \
--cc=idosch@nvidia.com \
--cc=julian@outer-limits.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skorodumov.dmitry@huawei.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).