From: patchwork-bot+netdevbpf@kernel.org
To: Nitin Shetty J <nshettyj@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
viswajithm@marvell.com, sgoutham@marvell.com,
rkannoth@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, vattunuru@marvell.com
Subject: Re: [PATCH net] octeontx2-af: mcs: Clear stale X2P calibration state before calibration
Date: Fri, 04 Sep 2026 22:50:31 +0000 [thread overview]
Message-ID: <178856223114.1003513.7113308179560566896.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260901094318.1395356-1-nshettyj@marvell.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Sep 2026 15:13:17 +0530 you wrote:
> From: Viswajith Murali <viswajithm@marvell.com>
>
> Some firmware versions leave MCSX_MIL_GLOBAL bit 5 set on boot.
> If the bit is already set when the driver attempts X2P calibration,
> the hardware sees no rising edge and calibration never triggers.
> Clear the bit and wait briefly before starting calibration to ensure
> a clean rising edge.
>
> [...]
Here is the summary with links:
- [net] octeontx2-af: mcs: Clear stale X2P calibration state before calibration
https://git.kernel.org/netdev/net/c/1f29543126dd
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:[~2026-09-04 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 9:43 [PATCH net] octeontx2-af: mcs: Clear stale X2P calibration state before calibration nshettyj
2026-09-04 22:50 ` 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=178856223114.1003513.7113308179560566896.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nshettyj@marvell.com \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=vattunuru@marvell.com \
--cc=viswajithm@marvell.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