From: Vinod Koul <vkoul@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: "Richard Zhu" <hongxing.zhu@nxp.com>, "Li Jun" <jun.li@nxp.com>,
"Guido Günther" <agx@sigxcpu.org>,
"Kishon Vijay Abraham I" <kishon@ti.com>,
linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: freescale: i.MX8 PHYs should depend on ARCH_MXC && ARM64
Date: Thu, 27 Jan 2022 11:05:27 +0530 [thread overview]
Message-ID: <YfIvH/f5ZoQQzUF1@matsya> (raw)
In-Reply-To: <393868affd830016d35f0d9aba32ccd7098c8073.1641987369.git.geert+renesas@glider.be>
On 12-01-22, 12:40, Geert Uytterhoeven wrote:
> The Freescale/NXP i.MX8 USB3, MIPI DSI, and PCIE PHYs are only present
> on the NXP i.MX8 family of SoCs. Hence wrap the config symbols for
> these PHYs inside a check for ARCH_MXC && ARM64, to prevent asking the
> user about these drivers when configuring a kernel without NXP i.MX SoC
> family support.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-01-27 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 11:40 [PATCH] phy: freescale: i.MX8 PHYs should depend on ARCH_MXC && ARM64 Geert Uytterhoeven
2022-01-12 14:20 ` Guido Günther
2022-01-27 5:35 ` 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=YfIvH/f5ZoQQzUF1@matsya \
--to=vkoul@kernel.org \
--cc=agx@sigxcpu.org \
--cc=geert+renesas@glider.be \
--cc=hongxing.zhu@nxp.com \
--cc=jun.li@nxp.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.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).