[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175089120849.644002.10005432355573220641.git-patchwork-notify@kernel.org>
Date: Wed, 25 Jun 2025 22:40:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Simon Horman <horms@...nel.org>
Cc: claudiu.manoil@....com, vladimir.oltean@....com, wei.fang@....com,
xiaoning.wang@....com, andrew+netdev@...n.ch, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
alexandru.marginean@....com, imx@...ts.linux.dev, netdev@...r.kernel.org
Subject: Re: [PATCH net] net: enetc: Correct endianness handling in
_enetc_rd_reg64
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 24 Jun 2025 17:35:12 +0100 you wrote:
> enetc_hw.h provides two versions of _enetc_rd_reg64.
> One which simply calls ioread64() when available.
> And another that composes the 64-bit result from ioread32() calls.
>
> In the second case the code appears to assume that each ioread32() call
> returns a little-endian value. However both the shift and logical or
> used to compose the return value would not work correctly on big endian
> systems if this were the case. Moreover, this is inconsistent with the
> first case where the return value of ioread64() is assumed to be in host
> byte order.
>
> [...]
Here is the summary with links:
- [net] net: enetc: Correct endianness handling in _enetc_rd_reg64
https://git.kernel.org/netdev/net/c/7b515f35a911
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists