From: Christoph Hellwig <hch@infradead.org>
To: Kunwu Chan <chentao@kylinos.cn>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jkbs@redhat.com,
kunwu.chan@hotmail.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ipv6: Correct/silence an endian warning in ip6_multipath_l3_keys
Date: Tue, 21 Nov 2023 23:23:05 -0800 [thread overview]
Message-ID: <ZV2sWSRzZhy4klrq@infradead.org> (raw)
In-Reply-To: <20231122071924.8302-1-chentao@kylinos.cn>
On Wed, Nov 22, 2023 at 03:19:24PM +0800, Kunwu Chan wrote:
> net/ipv6/route.c:2332:39: warning: incorrect type in assignment (different base types)
> net/ipv6/route.c:2332:39: expected unsigned int [usertype] flow_label
> net/ipv6/route.c:2332:39: got restricted __be32
Can you expain why you think the __force cast is the correct thing to do
here?
next prev parent reply other threads:[~2023-11-22 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 7:19 Kunwu Chan
2023-11-22 7:23 ` Christoph Hellwig [this message]
2023-11-22 9:04 ` Kunwu Chan
2023-11-22 9:06 ` Christoph Hellwig
2023-11-22 18:51 ` David Ahern
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=ZV2sWSRzZhy4klrq@infradead.org \
--to=hch@infradead.org \
--cc=chentao@kylinos.cn \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jkbs@redhat.com \
--cc=kuba@kernel.org \
--cc=kunwu.chan@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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®