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 v2 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries
Date: Fri, 26 Jun 2026 14:38:43 +0200 [thread overview]
Message-ID: <20260626143843.00006fd7@gmail.com> (raw)
In-Reply-To: <aj5v3rDRlY7H39Tq@ashevche-desk.local>
On Fri, 26 Jun 2026 15:26:06 +0300
Andy Shevchenko <andriy.shevchenko@intel.com> wrote:
> > 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 = {
> > | ^~~~~~~~~~~~~~~~~~~~
>
> Now all is better. The only thing is missing is Cc: stable@ line.
I knew I was missing something - must be the heat!
Hopefully Jonathan can mark it for stable while applying.
--
Kind regards
CJD
next prev parent reply other threads:[~2026-06-26 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 19:38 [PATCH v2 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries Joshua Crofts
2026-06-25 19:38 ` [PATCH v2 1/3] iio: light: al3000a: add missing REGMAP_I2C to Kconfig Joshua Crofts
2026-06-25 19:38 ` [PATCH v2 2/3] iio: light: al3010: " Joshua Crofts
2026-06-25 19:38 ` [PATCH v2 3/3] iio: light: al3320a: " Joshua Crofts
2026-06-25 19:50 ` [PATCH v2 0/3] iio: light: al3xxx: add missing REGMAP_I2C to Kconfig entries David Heidelberg
2026-06-26 12:26 ` Andy Shevchenko
2026-06-26 12:38 ` Joshua Crofts [this message]
2026-06-26 13:57 ` Nuno Sá
2026-06-26 14:13 ` Andy Shevchenko
2026-06-26 14:28 ` Joshua Crofts
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=20260626143843.00006fd7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox