mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jacopo Mondi <jacopo@jmondi.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH -next] iio: chemical: SENSEAIR_SUNRISE_CO2 depends on I2C
Date: Sun, 3 Oct 2021 16:37:31 +0100	[thread overview]
Message-ID: <20211003163731.289a5991@jic23-huawei> (raw)
In-Reply-To: <20211002232803.5108-1-rdunlap@infradead.org>

On Sat,  2 Oct 2021 16:28:03 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:

> Fix kconfig symbol dependency warning:
> 
> WARNING: unmet direct dependencies detected for REGMAP_I2C
>   Depends on [n]: I2C [=n]
>   Selected by [y]:
>   - SENSEAIR_SUNRISE_CO2 [=y] && IIO [=y]
> 
> Fixes: c3253a3fdc77 ("iio: chemical: Add Senseair Sunrise 006-0-007 drive")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jacopo Mondi <jacopo@jmondi.org>
> Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: linux-iio@vger.kernel.org

Thanks.  Applied to the togreg branch of iio.git.  I'll push that out
as testing for 0-day to run it's usual santity checks then push it out
for next to pick up.

Thanks,

Jonathan

> ---
>  drivers/iio/chemical/Kconfig |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- linux-next-20211001.orig/drivers/iio/chemical/Kconfig
> +++ linux-next-20211001/drivers/iio/chemical/Kconfig
> @@ -172,6 +172,7 @@ config SPS30_SERIAL
>  
>  config SENSEAIR_SUNRISE_CO2
>  	tristate "Senseair Sunrise 006-0-0007 CO2 sensor"
> +	depends on I2C
>  	select REGMAP_I2C
>  	help
>  	  Say yes here to build support for Senseair Sunrise 006-0-0007 CO2


      reply	other threads:[~2021-10-03 15:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 23:28 Randy Dunlap
2021-10-03 15:37 ` 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=20211003163731.289a5991@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=jacopo@jmondi.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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

all inboxes | Powered by JetHome®