[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<176956860860.1489558.7327500062965937708.git-patchwork-notify@kernel.org>
Date: Wed, 28 Jan 2026 02:50:08 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Harshitha Ramamurthy <hramamurthy@...gle.com>
Cc: netdev@...r.kernel.org, joshwash@...gle.com, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
richardcochran@...il.com, willemb@...gle.com, pkaligineedi@...gle.com,
ziweixiao@...gle.com, jordanrhee@...gle.com, nktgrg@...gle.com,
thostet@...gle.com, horms@...nel.org, yyd@...gle.com,
linux-kernel@...r.kernel.org, stable@...r.kernel.org, shacharr@...gle.com
Subject: Re: [PATCH net] gve: fix probe failure if clock read fails
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 27 Jan 2026 01:02:10 +0000 you wrote:
> From: Jordan Rhee <jordanrhee@...gle.com>
>
> If timestamping is supported, GVE reads the clock during probe,
> which can fail for various reasons. Previously, this failure would
> abort the driver probe, rendering the device unusable. This behavior
> has been observed on production GCP VMs, causing driver initialization
> to fail completely.
>
> [...]
Here is the summary with links:
- [net] gve: fix probe failure if clock read fails
https://git.kernel.org/netdev/net/c/a040afa3bca4
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