Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-renesas-soc@vger.kernel.org,
	Prabhakar <prabhakar.csengg@gmail.com>,
	Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH] iio: adc: Kconfig: Make RZG2L_ADC depend on ARCH_RZG2L
Date: Sun, 10 Apr 2022 17:47:13 +0100	[thread overview]
Message-ID: <20220410174713.1a4e013f@jic23-huawei> (raw)
In-Reply-To: <20220406070315.13862-1-prabhakar.mahadev-lad.rj@bp.renesas.com>

On Wed,  6 Apr 2022 08:03:15 +0100
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> wrote:

> ADC block is common on Renesas RZ/G2L and RZ/V2L SoC's, so instead of
> adding dependency for each SoC's add dependency on ARCH_RZG2L. The
> ARCH_RZG2L config option is already selected by ARCH_R9A07G044 and
> ARCH_R9A07G054.
> 
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Sounds like a fix?

If so, please supply a Fixes tag.
no need to resend, just reply with one to this email.

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 71ab0a06aa82..48ace7412874 100644
> --- a/drivers/iio/adc/Kconfig
> +++ b/drivers/iio/adc/Kconfig
> @@ -910,7 +910,7 @@ config ROCKCHIP_SARADC
>  
>  config RZG2L_ADC
>  	tristate "Renesas RZ/G2L ADC driver"
> -	depends on ARCH_R9A07G044 || COMPILE_TEST
> +	depends on ARCH_RZG2L || COMPILE_TEST
>  	help
>  	  Say yes here to build support for the ADC found in Renesas
>  	  RZ/G2L family.


  reply	other threads:[~2022-04-10 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  7:03 [PATCH] iio: adc: Kconfig: Make RZG2L_ADC depend on ARCH_RZG2L Lad Prabhakar
2022-04-10 16:47 ` Jonathan Cameron [this message]
2022-04-11 14:40   ` Geert Uytterhoeven
2022-04-16 11:23     ` 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=20220410174713.1a4e013f@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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