[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2ee5ec54d3aff6e37ec1245eeb019d52e6a3d63f.camel@foss.st.com>
Date: Sun, 23 Jun 2024 19:38:11 +0200
From: Antonio Borneo <antonio.borneo@...s.st.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Russell King
<linux@...linux.org.uk>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Catalin Marinas
<catalin.marinas@....com>,
Will Deacon <will@...nel.org>
CC: <linux-arm-kernel@...ts.infradead.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 7/8] ARM: stm32: allow build irq-stm32mp-exti driver
as module
On Sun, 2024-06-23 at 19:27 +0200, Thomas Gleixner wrote:
> 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?
In patch 6/8 it is already selected through:
+ depends on (ARCH_STM32 && !ARM_SINGLE_ARMV7M) || COMPILE_TEST
+ default y
Regards,
Antonio
Powered by blists - more mailing lists