From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: vkoul@kernel.org, neil.armstrong@linaro.org,
Robert Marko <robert.marko@sartura.hr>
Cc: kishon@kernel.org, geert+renesas@glider.be,
herve.codina@bootlin.com, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org, luka.perkov@sartura.hr,
Daniel Machon <daniel.machon@microchip.com>,
Gabor Juhos <j4g8y7@gmail.com>
Subject: Re: [PATCH v2] phy: sparx5-serdes: make it selectable for ARCH_LAN969X
Date: Sat, 6 Dec 2025 10:51:35 +0200 [thread overview]
Message-ID: <20251206085135.gxwsdhzi7k63tedq@skbuf> (raw)
In-Reply-To: <20251031121834.665987-1-robert.marko@sartura.hr>
On Fri, Oct 31, 2025 at 01:18:12PM +0100, Robert Marko wrote:
> LAN969x uses the SparX-5 SERDES driver, so make it selectable for
> ARCH_LAN969X.
>
> Reviewed-by: Daniel Machon <daniel.machon@microchip.com>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> ---
> Changes in v2:
> * Rebase onto next-20251031
> * Add Reviewed-by tag
>
> drivers/phy/microchip/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/microchip/Kconfig b/drivers/phy/microchip/Kconfig
> index 2f0045e874ac..2e6d1224711e 100644
> --- a/drivers/phy/microchip/Kconfig
> +++ b/drivers/phy/microchip/Kconfig
> @@ -6,7 +6,7 @@
> config PHY_SPARX5_SERDES
> tristate "Microchip Sparx5 SerDes PHY driver"
> select GENERIC_PHY
> - depends on ARCH_SPARX5 || COMPILE_TEST
> + depends on ARCH_SPARX5 || ARCH_LAN969X || COMPILE_TEST
> depends on OF
> depends on HAS_IOMEM
> help
> --
> 2.51.1
>
>
From what I'm able to tell this patch wasn't picked up, but the issue is
appearing in builds and should be addressed soon, with the Fixes: tag
that Gabor points out.
Tested-by: Vladimir Oltean <vladimir.oltean@nxp.com>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-12-06 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 12:18 [PATCH v2] phy: sparx5-serdes: make it selectable for ARCH_LAN969X Robert Marko
2025-10-31 12:48 ` Gabor Juhos
2025-12-06 8:51 ` Vladimir Oltean [this message]
2025-12-23 17:34 ` Vinod Koul
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=20251206085135.gxwsdhzi7k63tedq@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=daniel.machon@microchip.com \
--cc=geert+renesas@glider.be \
--cc=herve.codina@bootlin.com \
--cc=j4g8y7@gmail.com \
--cc=kishon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=luka.perkov@sartura.hr \
--cc=neil.armstrong@linaro.org \
--cc=robert.marko@sartura.hr \
--cc=vkoul@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