From: patchwork-bot+netdevbpf@kernel.org
To: Aksh Garg <a-garg7@ti.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, andrew+netdev@lunn.ch, edumazet@google.com,
linux-kernel@vger.kernel.org, c-vankar@ti.com,
s-vadapalli@ti.com, danishanwar@ti.com
Subject: Re: [PATCH net 0/2] Fix IET verification implementation for CPSW driver
Date: Tue, 11 Nov 2025 02:10:12 +0000 [thread overview]
Message-ID: <176282701275.2852248.9515452073916446665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251106092305.1437347-1-a-garg7@ti.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 6 Nov 2025 14:53:03 +0530 you wrote:
> The CPSW module supports Intersperse Express Traffic (IET) and allows
> the MAC layer to verify whether the peer supports IET through its MAC
> merge sublayer, by sending a verification packet and waiting for its
> response until the timeout. As defined in IEEE 802.3 Clause 99, the
> verification process involves up to 3 verification attempts to
> establish support.
>
> [...]
Here is the summary with links:
- [net,1/2] net: ethernet: ti: am65-cpsw-qos: fix IET verify/response timeout
https://git.kernel.org/netdev/net/c/49b391646517
- [net,2/2] net: ethernet: ti: am65-cpsw-qos: fix IET verify retry mechanism
https://git.kernel.org/netdev/net/c/d4b00d132d7c
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:[~2025-11-11 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 9:23 [PATCH net 0/2] Fix IET verification implementation for CPSW driver Aksh Garg
2025-11-06 9:23 ` [PATCH net 1/2] net: ethernet: ti: am65-cpsw-qos: fix IET verify/response timeout Aksh Garg
2025-11-06 9:23 ` [PATCH net 2/2] net: ethernet: ti: am65-cpsw-qos: fix IET verify retry mechanism Aksh Garg
2025-11-11 2:10 ` 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=176282701275.2852248.9515452073916446665.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a-garg7@ti.com \
--cc=andrew+netdev@lunn.ch \
--cc=c-vankar@ti.com \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=s-vadapalli@ti.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