From: patchwork-bot+netdevbpf@kernel.org
To: Nazle@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Asmade@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Muhammad Nazim Amirul
<muhammad.nazim.amirul.nazle.asmade@altera.com>
Cc: netdev@vger.kernel.org, rohan.g.thomas@altera.com,
pabeni@redhat.com, rmk+kernel@armlinux.org.uk,
richardcochran@gmail.com
Subject: Re: [PATCH net v2] net: stmmac: Fix E2E delay mechanism
Date: Thu, 30 Jul 2026 00:50:12 +0000 [thread overview]
Message-ID: <178537261239.3300615.14871055634290835947.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260728060904.31993-1-muhammad.nazim.amirul.nazle.asmade@altera.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 27 Jul 2026 23:09:04 -0700 you wrote:
> From: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
>
> For E2E delay mechanism, "received DELAY_REQ without timestamp" error
> messages show up for dwmac v3.70+ and dwxgmac IPs.
>
> This issue affects socfpga platforms, Agilex7 (dwmac 3.70) and
> Agilex5 (dwxgmac). According to the databook, to enable timestamping
> for all events, the SNAPTYPSEL bits in the MAC_Timestamp_Control
> register must be set to 2'b01, and the TSEVNTENA bit must be cleared
> to 0'b0.
>
> [...]
Here is the summary with links:
- [net,v2] net: stmmac: Fix E2E delay mechanism
https://git.kernel.org/netdev/net/c/b041ed62aa6e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-07-30 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 6:09 [PATCH net v2] net: stmmac: Fix E2E delay mechanism muhammad.nazim.amirul.nazle.asmade
2026-07-30 0:50 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-29 3:07 Rohan G Thomas via B4 Relay
2025-12-04 9:58 ` Paolo Abeni
2025-12-04 11:19 ` Russell King (Oracle)
2025-12-05 14:38 ` Richard Cochran
2025-12-09 12:31 ` G Thomas, Rohan
2025-12-09 13:01 ` Russell King (Oracle)
2025-12-09 12:27 ` G Thomas, Rohan
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=178537261239.3300615.14871055634290835947.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Asmade@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=Nazle@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=rohan.g.thomas@altera.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