From: Jakub Kicinski <kuba@kernel.org>
To: Rengarajan S <rengarajan.s@microchip.com>
Cc: <woojung.huh@microchip.com>, <UNGLinuxDriver@microchip.com>,
<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v1] lan78xx: lan7801 MAC support with lan8841
Date: Wed, 12 Jun 2024 18:33:09 -0700 [thread overview]
Message-ID: <20240612183309.01782254@kernel.org> (raw)
In-Reply-To: <20240611094233.865234-1-rengarajan.s@microchip.com>
On Tue, 11 Jun 2024 15:12:33 +0530 Rengarajan S wrote:
> /* define external phy id */
> #define PHY_LAN8835 (0x0007C130)
> +#define PHY_LAN8841 (0x00221650)
For whatever reason the existing code uses a tab between define and its
name, so let's stick to that?
> #define PHY_KSZ9031RNX (0x00221620)
>
> /* use ethtool to change the level for any given device */
> @@ -2327,6 +2328,13 @@ static struct phy_device *lan7801_phy_init(struct lan78xx_net *dev)
> netdev_err(dev->net, "Failed to register fixup for PHY_LAN8835\n");
> return NULL;
> }
> + /* external PHY fixup for LAN8841 */
> + ret = phy_register_fixup_for_uid(PHY_LAN8841, 0xfffffff0,
> + lan8835_fixup);
> + if (ret < 0) {
> + netdev_err(dev->net, "Failed to register fixup for PHY_LAN8841\n");
Don't you have to unregister the previous fixup on the error path here?
In fact the existing error path for PHY_LAN8835 is missing an unregsiter
for PHY_KSZ9031RNX.
Could you please send a separate fix for that with a Fixes tag?
> + return NULL;
> + }
next prev parent reply other threads:[~2024-06-13 1:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 9:42 [PATCH net-next v1] lan78xx: lan7801 MAC support with lan8841 Rengarajan S
2024-06-13 1:33 ` Jakub Kicinski [this message]
2024-06-20 5:33 ` Rengarajan.S
2024-06-13 20:46 ` Andrew Lunn
2024-06-20 5:48 ` Rengarajan.S
2024-06-20 13:49 ` Andrew Lunn
2024-06-28 10:59 ` Rengarajan.S
2024-06-28 13:03 ` Andrew Lunn
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=20240612183309.01782254@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rengarajan.s@microchip.com \
--cc=woojung.huh@microchip.com \
/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.