From: Nathan Chancellor <nathan@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Amit Kucheria <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Mark Brown <broonie@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
linux-iio@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH linux-next] thermal/drivers/qcom-spmi-mbg-tm: Add module namespace import for IIO_CONSUMER
Date: Thu, 13 Aug 2026 17:05:05 -0700 [thread overview]
Message-ID: <20260814000505.GA3919970@ax162> (raw)
In-Reply-To: <20260813023543.6936b188@jic23-huawei>
On Thu, Aug 13, 2026 at 02:35:43AM +0100, Jonathan Cameron wrote:
> I did plan for this being a possible issue:
>
> Ideal is merge
> https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git #iio-inkern-namespace-ib
> to the thermal tree. If I'd called that out originally (or a thermal
> rebase is a possibility) it would be cleaner to do this before the
> qcom patch adds another user then squash what you have here in the appropriate
> patch. Alternative is do it as a merge conflict resolution whilst merging
> in that tree. If the second, I'd also mention that in the thermal pull request to
> Linus given it's a little unusual.
Ah, I did not realize that you had a stable branch with the module
namespace patch. Merging that in then applying this to the thermal tree
seems like the best course of action. If rebasing is possible, I do not
mind this patch being squashed into the original.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-08-14 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 1:17 [PATCH linux-next] thermal/drivers/qcom-spmi-mbg-tm: Add module namespace import for IIO_CONSUMER Nathan Chancellor
2026-08-13 1:35 ` Jonathan Cameron
2026-08-14 0:05 ` Nathan Chancellor [this message]
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=20260814000505.GA3919970@ax162 \
--to=nathan@kernel.org \
--cc=amitk@kernel.org \
--cc=broonie@kernel.org \
--cc=daniel.lezcano@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@gmail.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