From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Randy Dunlap <rdunlap@infradead.org>, <linux-kernel@vger.kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH] arm64: STM32: drop an undefined Kconfig symbol
Date: Thu, 8 Jan 2026 18:09:50 +0100 [thread overview]
Message-ID: <eedd657d-158e-4391-b92c-593f22af715e@foss.st.com> (raw)
In-Reply-To: <20251230181429.3429404-1-rdunlap@infradead.org>
Hi
On 12/30/25 19:14, Randy Dunlap wrote:
> Drop ARM_SMC_MBOX since it is not defined or used anywhere else
> in the kernel source tree.
>
> Fixes: 9e4e24414cc6 ("arm64: introduce STM32 family on Armv8 architecture")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> Cc: linux-stm32@st-md-mailman.stormreply.com
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
>
> arch/arm64/Kconfig.platforms | 1 -
> 1 file changed, 1 deletion(-)
>
> --- linux-next-20251219.orig/arch/arm64/Kconfig.platforms
> +++ linux-next-20251219/arch/arm64/Kconfig.platforms
> @@ -372,7 +372,6 @@ config ARCH_STM32
> bool "STMicroelectronics STM32 SoC Family"
> select GPIOLIB
> select PINCTRL
> - select ARM_SMC_MBOX
> select ARM_SCMI_PROTOCOL
> select REGULATOR
> select REGULATOR_ARM_SCMI
Applied on stm32-next.
cheers
Alex
prev parent reply other threads:[~2026-01-08 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 18:14 Randy Dunlap
2026-01-08 17:09 ` Alexandre TORGUE [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=eedd657d-158e-4391-b92c-593f22af715e@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=rdunlap@infradead.org \
--cc=will@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
all inboxes | Powered by JetHome®