From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: Amit Kucheria <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Jonathan Cameron <jic23@kernel.org>,
Guenter Roeck <linux@roeck-us.net>, Vinod Koul <vkoul@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] thermal/drivers/qcom/spmi-mbg-tm: Import IIO_CONSUMER namespace
Date: Thu, 27 Aug 2026 15:52:42 +0300 [thread overview]
Message-ID: <apAzGkXpnMYHcnqJ@ashevche-desk.local> (raw)
In-Reply-To: <20260827103555.883018-1-shengchao.guo@oss.qualcomm.com>
On Thu, Aug 27, 2026 at 06:35:55PM +0800, Shawn Guo wrote:
> The IIO consumer interface symbols moved into the IIO_CONSUMER namespace,
> so consumers must import it explicitly. Without it modpost fails on
> 'iio_read_channel_processed' and 'devm_iio_channel_get':
iio_read_channel_processed()
devm_iio_channel_get()
> ERROR: modpost: drivers/thermal/qcom/qcom-spmi-mbg-tm.ko: module uses
> symbol 'iio_read_channel_processed' from namespace 'IIO_CONSUMER', but
> does not import it.
> Fixes: ebf1d03dab96 ("iio: inkern: Use namespaced exports")
Shouldn't this be backported to stable kernels?
...
Code wise looks good.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-08-27 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 10:35 [PATCH] thermal/drivers/qcom/spmi-mbg-tm: Import IIO_CONSUMER namespace Shawn Guo
2026-08-27 12:52 ` Andy Shevchenko [this message]
2026-08-27 14:35 ` Shawn Guo
2026-08-28 22:42 ` Jonathan Cameron
2026-08-29 9:56 ` Shawn Guo
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=apAzGkXpnMYHcnqJ@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sebastian.reichel@collabora.com \
--cc=shengchao.guo@oss.qualcomm.com \
--cc=thara.gopinath@gmail.com \
--cc=vkoul@kernel.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