[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <539a815398a3c991c1bc1a53967fbcba282dfe3b.camel@gmail.com>
Date: Wed, 29 May 2024 09:20:42 +0200
From: Nuno Sá <noname.nuno@...il.com>
To: Arnd Bergmann <arnd@...nel.org>, Jonathan Cameron <jic23@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, Lars-Peter Clausen <lars@...afoo.de>,
Nuno Sa <nuno.sa@...log.com>, Dragos Bogdan <dragos.bogdan@...log.com>,
Anshul Dalal <anshulusr@...il.com>, Andrea Collamati
<andrea.collamati@...il.com>, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] iio: dac: ad9739a: drop COMPILE_TEST option
On Tue, 2024-05-28 at 14:12 +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
>
> Build testing without SPI results in a warning:
>
> WARNING: unmet direct dependencies detected for REGMAP_SPI
> Depends on [n]: SPI [=n]
> Selected by [m]:
> - AD9739A [=m] && IIO [=m] && (SPI [=n] || COMPILE_TEST [=y])
>
> There is no need for this particular COMPILE_TEST option, as allmodconfig
> and randconfig testing can just assume that SPI is enabled separately.
>
> Drop it to avoid the warning.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>
> ---
Reviewed-by: Nuno Sa <nuno.sa@...log.com>
Only for my understanding. When does COMPILE_TEST makes sense to add?
- Nuno Sá
Powered by blists - more mailing lists