From: patchwork-bot+netdevbpf@kernel.org
To: huhai <15815827059@163.com>
Cc: kuba@kernel.org, andrew@lunn.ch, divya.koppera@microchip.com,
netdev@vger.kernel.org, xuanqiang.luo@linux.dev,
Divya.Koppera@microchip.com, huhai@kylinos.cn,
stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: phy: microchip_t1: fix NULL pointer dereference in lan887x_phy_init()
Date: Tue, 08 Sep 2026 00:30:09 +0000 [thread overview]
Message-ID: <178882740988.3220068.2607068471712359307.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903113046.163630-1-15815827059@163.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 3 Sep 2026 19:30:46 +0800 you wrote:
> From: Henry Hu <huhai@kylinos.cn>
>
> The issue was discovered via smatch static analyzer:
>
> make CHECK="smatch -p=kernel" C=2 drivers/net/phy/microchip_t1.o
> CHECK scripts/mod/empty.c
> DESCEND objtool
> CHECK drivers/net/phy/microchip_t1.c
> drivers/net/phy/microchip_t1.c:1295 lan887x_phy_init() warn: 'priv->clock' can also be NULL
>
> [...]
Here is the summary with links:
- [net,v2] net: phy: microchip_t1: fix NULL pointer dereference in lan887x_phy_init()
https://git.kernel.org/netdev/net-next/c/a4050ce7e46c
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-08 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:30 [PATCH net v2] net: phy: microchip_t1: fix NULL pointer dereference in lan887x_phy_init() huhai
2026-09-03 12:13 ` Xuanqiang Luo
2026-09-08 0:30 ` 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=178882740988.3220068.2607068471712359307.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=15815827059@163.com \
--cc=andrew@lunn.ch \
--cc=divya.koppera@microchip.com \
--cc=huhai@kylinos.cn \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xuanqiang.luo@linux.dev \
/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