[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174841878725.2284365.16902969225916201562.git-patchwork-notify@kernel.org>
Date: Wed, 28 May 2025 07:53:07 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
richardcochran@...il.com, kory.maincent@...tlin.com, wintera@...ux.ibm.com,
viro@...iv.linux.org.uk, quentin.schulz@...tlin.com, atenart@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net] net: phy: mscc: Stop clearing the the UDPv4 checksum for
L2 frames
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Fri, 23 May 2025 10:27:16 +0200 you wrote:
> We have noticed that when PHY timestamping is enabled, L2 frames seems
> to be modified by changing two 2 bytes with a value of 0. The place were
> these 2 bytes seems to be random(or I couldn't find a pattern). In most
> of the cases the userspace can ignore these frames but if for example
> those 2 bytes are in the correction field there is nothing to do. This
> seems to happen when configuring the HW for IPv4 even that the flow is
> not enabled.
> These 2 bytes correspond to the UDPv4 checksum and once we don't enable
> clearing the checksum when using L2 frames then the frame doesn't seem
> to be changed anymore.
>
> [...]
Here is the summary with links:
- [net] net: phy: mscc: Stop clearing the the UDPv4 checksum for L2 frames
https://git.kernel.org/netdev/net/c/57a92d14659d
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