From: Shawn Guo <shawnguo2@yeah.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"Sudeep Holla" <sudeep.holla@arm.com>,
"Mark Brown" <broonie@kernel.org>,
soc@lists.linux.dev, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend] firmware: imx: IMX_SCMI_MISC_DRV should depend on ARCH_MXC
Date: Sun, 23 Feb 2025 20:22:51 +0800 [thread overview]
Message-ID: <Z7sTG4yMsek11nLe@dragon> (raw)
In-Reply-To: <CAMuHMdW=ZH7D+m54rh-25nFShCYhRhEjkjaB1LtOrRF5RyrXiQ@mail.gmail.com>
+ Uwe
On Sun, Feb 23, 2025 at 09:29:29AM +0100, Geert Uytterhoeven wrote:
> Hi Shawn,
>
> On Sun, 23 Feb 2025 at 08:21, Shawn Guo <shawnguo2@yeah.net> wrote:
> > On Wed, Feb 05, 2025 at 03:41:43PM +0100, Geert Uytterhoeven wrote:
> > > The i.MX System Controller Management Interface firmware is only present
> > > on Freescale i.MX SoCs. Hence add a dependency on ARCH_MXC, to prevent
> > > asking the user about this driver when configuring a kernel without
> > > Freescale i.MX platform support.
> > >
> > > Fixes: 514b2262ade48a05 ("firmware: arm_scmi: Fix i.MX build dependency")
> > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
> > Thanks for the patch, Geert! But I have just picked up the change from
> > Uwe [1].
>
> Thanks, but mine has been upstream since Friday ;-)
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be6686b823b30a69b1f71bde228ce042c78a1941
Ah, Arnd beat me to it. Thanks for information!
Shawn
prev parent reply other threads:[~2025-02-23 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 14:41 [PATCH resend] firmware: imx: IMX_SCMI_MISC_DRV should depend on ARCH_MXC Geert Uytterhoeven
2025-02-05 15:50 ` Fabio Estevam
2025-02-23 7:21 ` Shawn Guo
2025-02-23 8:29 ` Geert Uytterhoeven
2025-02-23 12:22 ` Shawn Guo [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=Z7sTG4yMsek11nLe@dragon \
--to=shawnguo2@yeah.net \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=geert@linux-m68k.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=soc@lists.linux.dev \
--cc=sudeep.holla@arm.com \
--cc=u.kleine-koenig@baylibre.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;
as well as URLs for NNTP newsgroup(s).