From: Vinod Koul <vkoul@kernel.org>
To: linux-phy@lists.infradead.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, "Paolo Abeni" <pabeni@redhat.com>,
"Bjørn Mork" <bjorn@mork.no>,
linux-kernel@vger.kernel.org,
"Venkat Rao Bagalkote" <venkat88@linux.ibm.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
Subject: Re: [PATCH phy] phy: enter drivers/phy/Makefile even without CONFIG_GENERIC_PHY
Date: Wed, 04 Feb 2026 21:14:03 +0530 [thread overview]
Message-ID: <177021984348.133434.2174228638477842176.b4-ty@kernel.org> (raw)
In-Reply-To: <20260123110600.3118561-1-vladimir.oltean@nxp.com>
On Fri, 23 Jan 2026 13:06:00 +0200, Vladimir Oltean wrote:
> Kconfig option CONFIG_PHY_COMMON_PROPS, which builds
> drivers/phy/phy-common-props.c, was intended to be selectable
> independently of CONFIG_GENERIC_PHY. Yet it lives in drivers/phy/, which
> is entered by the Makefile only if CONFIG_GENERIC_PHY is set.
>
> Allow the Makefile to enter one level deeper, but stop at drivers/phy/
> if CONFIG_GENERIC_PHY is unselected (i.e. do not enter vendor folders).
> The other stuff from drivers/phy/Makefile except for CONFIG_PHY_COMMON_PROPS,
> like CONFIG_PHY_NXP_PTN3222, all depends on CONFIG_GENERIC_PHY.
>
> [...]
Applied, thanks!
[1/1] phy: enter drivers/phy/Makefile even without CONFIG_GENERIC_PHY
commit: 3ddcd24b4d8454b2b9b2d013a0d61986ae8bbbe7
Best regards,
--
~Vinod
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2026-02-04 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 11:06 [PATCH phy] phy: enter drivers/phy/Makefile even without CONFIG_GENERIC_PHY Vladimir Oltean
2026-01-23 11:09 ` Christophe Leroy (CS GROUP)
2026-01-23 13:01 ` Venkat Rao Bagalkote
2026-02-03 9:56 ` Venkat Rao Bagalkote
2026-02-03 12:25 ` Mark Brown
2026-02-04 15:44 ` Vinod Koul [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=177021984348.133434.2174228638477842176.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=bjorn@mork.no \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=venkat88@linux.ibm.com \
--cc=vladimir.oltean@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox