All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Crofts <joshua.crofts1@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Svyatoslav Ryhel" <clamor95@gmail.com>,
	"David Heidelberg" <david@ixit.cz>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries
Date: Thu, 25 Jun 2026 08:53:29 +0200	[thread overview]
Message-ID: <20260625085329.00007959@gmail.com> (raw)
In-Reply-To: <ajzNmy3Vhh_Zl9Rs@ashevche-desk.local>

On Thu, 25 Jun 2026 09:41:31 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:

> On Thu, Jun 25, 2026 at 07:20:42AM +0200, Joshua Crofts wrote:
> > This series adds REGMAP_I2C support to three AL3xxx ambient light
> > sensors that were previously missing this dependency, causing build
> > failures.  
> 
> There are two problems with the commit message:
> - SELECT versus select (see the comment against patch 1)
> - you mentioned build failures but haven't provided any evidence, please
> provide a reasonable lines of build output to prove that
> 

Sure, I could elaborate a bit more.

Just run `make allnoconfig` and `make menuconfig` in which you select
IIO, I2C and any AL3xxx sensor and `make .` will fail with errors such as

drivers/iio/light/al3010.c: In function ‘al3010_probe’:
drivers/iio/light/al3010.c:185:24: error: implicit declaration of function ‘devm_regmap_init_i2c’ [-Wimplicit-function-declaration]
  185 |         data->regmap = devm_regmap_init_i2c(client, &al3010_regmap_config);
      |                        ^~~~~~~~~~~~~~~~~~~~
drivers/iio/light/al3010.c:185:22: error: assignment to ‘struct regmap *’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
  185 |         data->regmap = devm_regmap_init_i2c(client, &al3010_regmap_config);
      |                      ^
drivers/iio/light/al3010.c: At top level:
drivers/iio/light/al3010.c:48:35: error: storage size of ‘al3010_regmap_config’ isn’t known
   48 | static const struct regmap_config al3010_regmap_config = {
      |                                   ^~~~~~~~~~~~~~~~~~~~

Hopefully this is enough.

-- 
Kind regards

CJD

  reply	other threads:[~2026-06-25  6:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25  5:20 [PATCH 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries Joshua Crofts
2026-06-25  5:20 ` [PATCH 1/3] iio: light: al3000a: add missing REGMAP_I2C to Kconfig Joshua Crofts
2026-06-25  6:39   ` Andy Shevchenko
2026-06-25  6:43     ` Joshua Crofts
2026-06-25  5:20 ` [PATCH 2/3] iio: light: al3010: " Joshua Crofts
2026-06-25  5:20 ` [PATCH 3/3] iio: light: al3320a: " Joshua Crofts
2026-06-25  6:41 ` [PATCH 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries Andy Shevchenko
2026-06-25  6:53   ` Joshua Crofts [this message]
2026-06-25  7:01     ` Andy Shevchenko

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=20260625085329.00007959@gmail.com \
    --to=joshua.crofts1@gmail.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=clamor95@gmail.com \
    --cc=david@ixit.cz \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.