From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, "Andy Shevchenko" <andy@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH 1/2] iio: magn: mmc5633: Ensure REGMAP_I2C / I3C not build if I2C / I3C is not.
Date: Tue, 20 Jan 2026 09:23:35 +0200 [thread overview]
Message-ID: <aW8td75ZhKd1mIMW@smile.fi.intel.com> (raw)
In-Reply-To: <20260119221736.804825-2-jic23@kernel.org>
On Mon, Jan 19, 2026 at 10:17:35PM +0000, Jonathan Cameron wrote:
> Fixes the following build warning (and equivalent I2C one)
> WARNING: unmet direct dependencies detected for REGMAP_I3C
> Depends on [n]: I3C [=n]
> Selected by [m]:
> - MMC5633 [=m] && IIO [=y] && (I2C [=y] || I3C [=n])
Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-20 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 22:17 [PATCH 0/2] iio: magn: mmc5633: Fix two build issues Jonathan Cameron
2026-01-19 22:17 ` [PATCH 1/2] iio: magn: mmc5633: Ensure REGMAP_I2C / I3C not build if I2C / I3C is not Jonathan Cameron
2026-01-20 7:23 ` Andy Shevchenko [this message]
2026-01-31 12:18 ` Jonathan Cameron
2026-01-19 22:17 ` [PATCH 2/2] iio: magn: mmc5633: Add some ifdef / __maybe_unused until stubs available Jonathan Cameron
2026-01-20 7:23 ` Andy Shevchenko
2026-01-20 21:56 ` Jonathan Cameron
2026-01-20 22:03 ` Jonathan Cameron
2026-01-21 20:01 ` Jonathan Cameron
2026-01-19 23:00 ` [PATCH 0/2] iio: magn: mmc5633: Fix two build issues Frank Li
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=aW8td75ZhKd1mIMW@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=Frank.Li@nxp.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@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