From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org
Cc: "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: [PATCH 0/2] iio: magn: mmc5633: Fix two build issues
Date: Mon, 19 Jan 2026 22:17:34 +0000 [thread overview]
Message-ID: <20260119221736.804825-1-jic23@kernel.org> (raw)
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
The Kconfig issue was one I came across whilst testing the second fix
which has been being reported by the bots for some time. Frank posted the
full fix for the undefined symbols a while back, but it is merged in
the middle i3c/for-next making it hard to merge into IIO as well.
So work around this to get the build issue resolved.
That workaround can be reverted next cycle.
I'll queue these up now but they can have brief 0-day exposure
before I push them out on the togreg branch to be picked up by
linux-next. Even after that comments on these ones welcome.
Thanks,
Jonathan
Jonathan Cameron (2):
iio: magn: mmc5633: Ensure REGMAP_I2C / I3C not build if I2C / I3C is
not.
iio: magn: mmc5633: Add some ifdef / __maybe_unused until stubs
available
drivers/iio/magnetometer/Kconfig | 4 ++--
drivers/iio/magnetometer/mmc5633.c | 25 +++++++++++++++++++++----
2 files changed, 23 insertions(+), 6 deletions(-)
--
2.52.0
next reply other threads:[~2026-01-19 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 22:17 Jonathan Cameron [this message]
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
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=20260119221736.804825-1-jic23@kernel.org \
--to=jic23@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--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