From: Thomas Gleixner <tglx@linutronix.de>
To: Antonio Borneo <antonio.borneo@foss.st.com>,
Russell King <linux@armlinux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Cc: Antonio Borneo <antonio.borneo@foss.st.com>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/8] ARM: stm32: allow build irq-stm32mp-exti driver as module
Date: Sun, 23 Jun 2024 19:27:18 +0200 [thread overview]
Message-ID: <87le2va7t5.ffs@tglx> (raw)
In-Reply-To: <20240620083115.204362-8-antonio.borneo@foss.st.com>
On Thu, Jun 20 2024 at 10:31, Antonio Borneo wrote:
> Drop auto-selecting the driver, so it can be built either as a
> module or built-in.
How is the driver selected then? Has this to be done manually now?
If so, doesn't that break things when starting from an empty config?
Thanks,
tglx
next prev parent reply other threads:[~2024-06-23 17:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 8:31 [PATCH v3 0/8] irqchip/stm32-exti: split MCU and MPU code, allow module build Antonio Borneo
2024-06-20 8:31 ` [PATCH v3 1/8] irqchip/stm32-exti: add CONFIG_STM32MP_EXTI Antonio Borneo
2024-06-20 8:31 ` [PATCH v3 2/8] ARM: stm32: use different EXTI driver on ARMv7m and ARMv7a Antonio Borneo
2024-06-20 8:31 ` [PATCH v3 3/8] arm64: Kconfig: select STM32MP_EXTI on STM32 platforms Antonio Borneo
2024-06-20 8:31 ` [PATCH v3 4/8] irqchip/stm32-exti: split MCU and MPU code Antonio Borneo
2024-06-20 8:31 ` [PATCH v3 5/8] irqchip/stm32mp-exti: rename internal symbols Antonio Borneo
2024-06-20 8:31 ` [PATCH v3 6/8] irqchip/stm32mp-exti: allow build as module Antonio Borneo
2024-06-20 8:31 ` [PATCH v3 7/8] ARM: stm32: allow build irq-stm32mp-exti driver " Antonio Borneo
2024-06-23 17:27 ` Thomas Gleixner [this message]
2024-06-23 17:38 ` Antonio Borneo
2024-06-23 22:15 ` Thomas Gleixner
2024-06-20 8:31 ` [PATCH v3 8/8] arm64: Kconfig: " Antonio Borneo
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=87le2va7t5.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=antonio.borneo@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=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--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