[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167652541903.5481.7404304709458067270.git-patchwork-notify@kernel.org>
Date: Thu, 16 Feb 2023 05:30:19 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Dan Carpenter <error27@...il.com>
Cc: Frank.Sae@...or-comm.com, andrew@...n.ch, hkallweit1@...il.com,
linux@...linux.org.uk, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, netdev@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH v2 net-next] net: phy: motorcomm: uninitialized variables in
yt8531_link_change_notify()
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@...nel.org>:
On Wed, 15 Feb 2023 07:21:47 +0300 you wrote:
> These booleans are never set to false, but are just used without being
> initialized.
>
> Fixes: 4ac94f728a58 ("net: phy: Add driver for Motorcomm yt8531 gigabit ethernet phy")
> Signed-off-by: Dan Carpenter <error27@...il.com>
> ---
> v2: reverse Christmas tree. Also add "motorcomm" to the subject. It
> really feels like previous patches to this driver should have had
> motorcomm in the subject as well. It's a common anti-pattern to only
> put the subsystem name and not the driver name when adding a new file.
>
> [...]
Here is the summary with links:
- [v2,net-next] net: phy: motorcomm: uninitialized variables in yt8531_link_change_notify()
https://git.kernel.org/netdev/net-next/c/9753613f7399
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