[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190912100308.GJ2036@sirena.org.uk>
Date: Thu, 12 Sep 2019 11:03:08 +0100
From: Mark Brown <broonie@...nel.org>
To: Arnd Bergmann <arnd@...db.de>
Cc: Amit Kucheria <amit.kucheria@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
arm-soc <arm@...nel.org>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Catalin Marinas <catalin.marinas@....com>,
Kishon Vijay Abraham I <kishon@...com>,
Liam Girdwood <lgirdwood@...il.com>,
Linus Walleij <linus.walleij@...aro.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Michael Turquette <mturquette@...libre.com>,
Sebastian Reichel <sre@...nel.org>,
Stephen Boyd <sboyd@...nel.org>, Will Deacon <will@...nel.org>,
linux-clk <linux-clk@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
linux-pci <linux-pci@...r.kernel.org>,
Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 0/4] Cleanup arm64 driver dependencies
On Thu, Sep 12, 2019 at 11:29:00AM +0200, Arnd Bergmann wrote:
> Generally speaking, the way that works best is
> config SUBSYS_DRIVER_FOO
> tristate "SUBSYS support for FOO platform"
> depends on ARCH_FOO || COMPILE_TEST
> depends on SUBSYS
> default "m" if ARCH_FOO
> This means it's enabled as a loadable module by default (use
> default "y" instead where necessary) as long as the platform
> is enabled, but an x86 allmodconfig build also includes it
> because of COMPILE_TEST, while any configuration without
> ARCH_FOO that is not compile-testing cannot enable it.
Indeed, though we shouldn't be adding any default m/y to things
that don't already default on.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists