public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: Arnd Bergmann <arnd@kernel.org>, Jonathan Cameron <jic23@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	 Nuno Sa <nuno.sa@analog.com>,
	Dragos Bogdan <dragos.bogdan@analog.com>,
	Anshul Dalal <anshulusr@gmail.com>,
	Andrea Collamati <andrea.collamati@gmail.com>,
	 linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: dac: ad9739a: drop COMPILE_TEST option
Date: Wed, 29 May 2024 09:20:42 +0200	[thread overview]
Message-ID: <539a815398a3c991c1bc1a53967fbcba282dfe3b.camel@gmail.com> (raw)
In-Reply-To: <20240528121304.3695252-1-arnd@kernel.org>

On Tue, 2024-05-28 at 14:12 +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.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@arndb.de>
> ---

Reviewed-by: Nuno Sa <nuno.sa@analog.com>

Only for my understanding. When does COMPILE_TEST makes sense to add?

- Nuno Sá


  reply	other threads:[~2024-05-29  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 12:12 [PATCH] iio: dac: ad9739a: drop COMPILE_TEST option Arnd Bergmann
2024-05-29  7:20 ` Nuno Sá [this message]
2024-05-29  7:23   ` Arnd Bergmann
2024-05-29  8:09     ` Nuno Sá
2024-06-02 12:14       ` Jonathan Cameron

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=539a815398a3c991c1bc1a53967fbcba282dfe3b.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=andrea.collamati@gmail.com \
    --cc=anshulusr@gmail.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=dragos.bogdan@analog.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    /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