From: Jonathan Cameron <jic23@kernel.org>
To: Alexandru Ardelean <aardelean@deviqon.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/2] iio: adc: Kconfig: add COMPILE_TEST dep for berlin2-adc
Date: Thu, 30 Sep 2021 17:29:08 +0100 [thread overview]
Message-ID: <20210930172908.10a31910@jic23-huawei> (raw)
In-Reply-To: <20210926192642.4051329-2-aardelean@deviqon.com>
On Sun, 26 Sep 2021 22:26:42 +0300
Alexandru Ardelean <aardelean@deviqon.com> wrote:
> Otherwise most build checks will omit this driver from a compile-test due
> to it's dependency only on the BERLIN_ARCH symbol.
>
> Signed-off-by: Alexandru Ardelean <aardelean@deviqon.com>
I was rather expecting this to need more dependencies, but I can't find
anything that isn't appropriately stubbed out.
Guess time to let 0-day and it's brute force builds work their magic.
Series applied to the togreg branch of iio.git and pushed out as testing to
see if we did miss a select or two in here.
Thanks,
Jonathan
> ---
> drivers/iio/adc/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
> index 0ceea8e69e3c..8bf5b62a73f4 100644
> --- a/drivers/iio/adc/Kconfig
> +++ b/drivers/iio/adc/Kconfig
> @@ -354,7 +354,7 @@ config BCM_IPROC_ADC
>
> config BERLIN2_ADC
> tristate "Marvell Berlin2 ADC driver"
> - depends on ARCH_BERLIN
> + depends on ARCH_BERLIN || COMPILE_TEST
> help
> Marvell Berlin2 ADC driver. This ADC has 8 channels, with one used for
> temperature measurement.
prev parent reply other threads:[~2021-09-30 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 19:26 [PATCH 1/2] iio: adc: berlin2-adc: convert probe to device-managed only Alexandru Ardelean
2021-09-26 19:26 ` [PATCH 2/2] iio: adc: Kconfig: add COMPILE_TEST dep for berlin2-adc Alexandru Ardelean
2021-09-30 16:29 ` Jonathan Cameron [this message]
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=20210930172908.10a31910@jic23-huawei \
--to=jic23@kernel.org \
--cc=aardelean@deviqon.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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