From: patchwork-bot+netdevbpf@kernel.org
To: Sudeep Holla <Sudeep.Holla@arm.com>
Cc: linux-kernel@vger.kernel.org, sudeep.holla@arm.com,
gregkh@linuxfoundation.org, andrew@lunn.ch, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [RESEND PATCH] net: phy: fixed_phy: transition to the faux device interface
Date: Mon, 24 Mar 2025 21:00:34 +0000 [thread overview]
Message-ID: <174285003475.4171308.4781336832128708063.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250319135209.2734594-1-sudeep.holla@arm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Mar 2025 13:52:09 +0000 you wrote:
> The net fixed phy driver does not require the creation of a platform
> device. Originally, this approach was chosen for simplicity when the
> driver was first implemented.
>
> With the introduction of the lightweight faux device interface, we now
> have a more appropriate alternative. Migrate the device to utilize the
> faux bus, given that the platform device it previously created was not
> a real one anyway. This will get rid of the fake platform device.
>
> [...]
Here is the summary with links:
- [RESEND] net: phy: fixed_phy: transition to the faux device interface
https://git.kernel.org/netdev/net-next/c/c4ebde35085e
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:[~2025-03-24 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 13:52 [RESEND PATCH] net: phy: fixed_phy: transition to the faux device interface Sudeep Holla
2025-03-24 21:00 ` 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=174285003475.4171308.4781336832128708063.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Sudeep.Holla@arm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).