From: patchwork-bot+netdevbpf@kernel.org
To: Arun Ramadoss <arun.ramadoss@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
kuba@kernel.org, davem@davemloft.net,
UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next 0/2] net: phy: lan87xx: use genphy_read_master_slave function
Date: Tue, 08 Mar 2022 14:30:10 +0000 [thread overview]
Message-ID: <164674981050.5894.8714803108771369458.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220307161515.14970-1-arun.ramadoss@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 7 Mar 2022 21:45:13 +0530 you wrote:
> LAN87xx T1 Phy has the same register field as gigabit phy for reading the
> master slave configuration. But the genphy_read_master_slave function has a
> check of gigabit phy. So refactored the function in such a way, moved the speed
> check to the genphy_read_status function. Analyzed the nxp-tja11xx function for
> refactoring, but the register for configuring master/slave is nxp specific
> which is not extended phy register.
> And analyzed the reusing genphy_setup_master_slave, but for LAN87xx
> MASTER_ENABLE is always 1 and Preferred state is always 0. So, I didn't try to
> change it.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: phy: exported the genphy_read_master_slave function
https://git.kernel.org/netdev/net-next/c/64807c232151
- [net-next,2/2] net: phy: lan87xx: use genphy_read_master_slave in read_status
https://git.kernel.org/netdev/net-next/c/f1f3a674261e
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-03-08 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 16:15 [PATCH net-next 0/2] net: phy: lan87xx: use genphy_read_master_slave function Arun Ramadoss
2022-03-07 16:15 ` [PATCH net-next 1/2] net: phy: exported the " Arun Ramadoss
2022-03-07 16:29 ` Andrew Lunn
2022-03-07 16:15 ` [PATCH net-next 2/2] net: phy: lan87xx: use genphy_read_master_slave in read_status Arun Ramadoss
2022-03-08 14: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=164674981050.5894.8714803108771369458.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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