Re: linux-next: Tree for Aug 21 (drivers/thermal/qcom/qcom-spmi-mbg-tm.ko)

"Rafael J. Wysocki (Intel)" <[email protected]>
Newsgroups org.kernel.vger.linux-pm,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-kernel,org.kernel.vger.linux-next
Message-ID <CAJZ5v0gDQAbyo+KTgQ8CzUfJ6cv4xg6-rHbH-HcbfXCWX9Wc7g@mail.gmail.com>
On Tue, Aug 25, 2026 at 8:48 PM Nathan Chancellor <[email protected]> wrote:
>
> On Tue, Aug 25, 2026 at 03:27:32PM +0200, Rafael J. Wysocki wrote:
> > On Monday, August 24, 2026 9:15:16 PM CEST Randy Dunlap wrote:
> > >
> > > On 8/21/26 8:32 AM, Mark Brown wrote:
> > > > Hi all,
> > > >
> > > > Changes since 20260820:
> > > >
> > > > None.
> > > >
> > > > Non-merge commits (relative to Linus' tree): 7073
> > > >  5989 files changed, 509370 insertions(+), 156446 deletions(-)
> > >
> > > on x86_64 allmodconfig:
> > >
> > > WARNING: modpost: drivers/thermal/qcom/qcom-spmi-mbg-tm.ko: module uses symbol 'devm_iio_channel_get' from namespace 'IIO_CONSUMER', but does not import it.
> > > WARNING: 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.
> >
> > Does the appended patch address it?
> >
> > Interestingly enough, it doesn't complain for me when I build the
> > thermal tree merged on top of the current mainline.
>
> FWIW, I sent a fix for this two weeks ago that explains the semantic
> conflict:
>
>   https://lore.kernel.org/20260812-qcom-spmi-mbg-tm-ns-modpost-error-v1-1-d849390d2714@kernel.org/
>
> You will only see it when the IIO tree is merged against the thermal
> tree.

I missed that one, thanks for the pointer!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.