From: patchwork-bot+netdevbpf@kernel.org
To: Fabio Estevam <festevam@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, andrew@lunn.ch,
netdev@vger.kernel.org, festevam@denx.de
Subject: Re: [PATCH net-next 1/2] net: phy: micrel: Allow probing without .driver_data
Date: Mon, 16 May 2022 20:10:12 +0000 [thread overview]
Message-ID: <165273181239.30267.5350054361391896735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220513114613.762810-1-festevam@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 13 May 2022 08:46:12 -0300 you wrote:
> From: Fabio Estevam <festevam@denx.de>
>
> Currently, if the .probe element is present in the phy_driver structure
> and the .driver_data is not, a NULL pointer dereference happens.
>
> Allow passing .probe without .driver_data by inserting NULL checks
> for priv->type.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: phy: micrel: Allow probing without .driver_data
https://git.kernel.org/netdev/net-next/c/f2ef6f7539c6
- [net-next,2/2] net: phy: micrel: Use the kszphy probe/suspend/resume
https://git.kernel.org/netdev/net-next/c/8e6004dfecb7
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:[~2022-05-16 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 11:46 [PATCH net-next 1/2] net: phy: micrel: Allow probing without .driver_data Fabio Estevam
2022-05-13 11:46 ` [PATCH net-next 2/2] net: phy: micrel: Use the kszphy probe/suspend/resume Fabio Estevam
2022-05-13 19:37 ` Andrew Lunn
2022-05-13 19:36 ` [PATCH net-next 1/2] net: phy: micrel: Allow probing without .driver_data Andrew Lunn
2022-05-16 20: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=165273181239.30267.5350054361391896735.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=festevam@denx.de \
--cc=festevam@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.