From: patchwork-bot+netdevbpf@kernel.org
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: davem@davemloft.net, kuba@kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
charlie@rivosinc.com, palmer@dabbelt.com, erhard_f@mailbox.org
Subject: Re: [PATCH net] kunit: Fix again checksum tests on big endian CPUs
Date: Thu, 29 Feb 2024 17:40:31 +0000 [thread overview]
Message-ID: <170922843125.9358.2716683497348325384.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <73df3a9e95c2179119398ad1b4c84cdacbd8dfb6.1708684443.git.christophe.leroy@csgroup.eu>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 23 Feb 2024 11:41:52 +0100 you wrote:
> Commit b38460bc463c ("kunit: Fix checksum tests on big endian CPUs")
> fixed endianness issues with kunit checksum tests, but then
> commit 6f4c45cbcb00 ("kunit: Add tests for csum_ipv6_magic and
> ip_fast_csum") introduced new issues on big endian CPUs. Those issues
> are once again reflected by the warnings reported by sparse.
>
> So, fix them with the same approach, perform proper conversion in
> order to support both little and big endian CPUs. Once the conversions
> are properly done and the right types used, the sparse warnings are
> cleared as well.
>
> [...]
Here is the summary with links:
- [net] kunit: Fix again checksum tests on big endian CPUs
https://git.kernel.org/netdev/net/c/3d6423ef8d51
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-02-29 17:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 10:41 [PATCH net] kunit: Fix again checksum tests on big endian CPUs Christophe Leroy
2024-02-23 17:57 ` Charlie Jenkins
2024-02-23 18:15 ` Christophe Leroy
2024-02-23 20:05 ` Charlie Jenkins
2024-02-24 7:40 ` Christophe Leroy
2024-02-24 7:44 ` Christophe Leroy
2024-02-27 9:06 ` Paolo Abeni
2024-02-29 1:51 ` Jakub Kicinski
2024-02-29 1:55 ` Palmer Dabbelt
2024-02-25 15:58 ` Guenter Roeck
2024-02-29 17:40 ` patchwork-bot+netdevbpf [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=170922843125.9358.2716683497348325384.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=charlie@rivosinc.com \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=erhard_f@mailbox.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.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