From: Hans de Goede <johannes.goede@oss.qualcomm.com>
To: "Sudeep Holla" <sudeep.holla@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Bjorn Andersson" <andersson@kernel.org>,
"Cristian Marussi" <cristian.marussi@arm.com>,
"Daniel Lezcano" <daniel.lezcano@oss.qualcomm.com>,
"Bjorn Andersson" <bjorn.andersson@oss.qualcomm.com>,
Frank.Li@kernel.org, arm-scmi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] module: add SCMI device table alias support
Date: Wed, 23 Sep 2026 17:42:15 +0200 [thread overview]
Message-ID: <839b884b-9db0-4215-9715-40549d1c6a26@oss.qualcomm.com> (raw)
In-Reply-To: <20260923-groovy-airborne-rook-e1efc6@sudeepholla>
Hi,
On 23-Sep-26 16:25, Sudeep Holla wrote:
> On Wed, Sep 23, 2026 at 02:55:26PM +0200, Uwe Kleine-König wrote:
>> On Wed, Sep 23, 2026 at 01:01:44PM +0100, Sudeep Holla wrote:
>>> If Uwe is fine, yes I can take v7 as is.
>>
>> Fine for me.
>>
>> Acked-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
>>
>
> Thanks Uwe!
>
>> The nice thing is that the device_id structs are not API, so this can
>> also be addressed later if someone comes up with a clever idea how to
>> implement it.
>>
>
> Agreed.
>
> Hans,
>
> There were other changes in bus.c that conflicted with this. I have
> resolved the conflicts and pushed to my for-next/scmi/updates[1]
>
> If anything is wrong or if you prefer, you can post a rebased version
> that I can pick up.
I've given your for-next/scmi/updates branch a test run and
the scmi-cpufreq module autuloads correctly, so everything is looking
good from my pov.
Regards,
Hans
next prev parent reply other threads:[~2026-09-23 15:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 9:29 [PATCH v7 0/2] firmware: arm_scmi: fix module auto-loading Hans de Goede
2026-09-18 9:29 ` [PATCH v7 1/2] module: add SCMI device table alias support Hans de Goede
2026-09-18 9:53 ` Daniel Lezcano
2026-09-18 10:02 ` Hans de Goede
2026-09-18 10:13 ` Daniel Lezcano
2026-09-18 13:38 ` Sudeep Holla
2026-09-18 14:43 ` Rob Clark
2026-09-18 14:48 ` Daniel Lezcano
2026-09-18 20:15 ` Daniel Lezcano
2026-09-18 13:32 ` Sudeep Holla
2026-09-18 14:09 ` Hans de Goede
2026-09-18 20:39 ` Uwe Kleine-König
2026-09-20 7:36 ` Sudeep Holla
2026-09-20 10:18 ` Uwe Kleine-König
2026-09-21 8:28 ` Sudeep Holla
2026-09-21 15:19 ` Uwe Kleine-König
2026-09-23 9:07 ` Sudeep Holla
2026-09-23 10:23 ` Hans de Goede
2026-09-23 10:49 ` Sudeep Holla
2026-09-23 11:26 ` Hans de Goede
2026-09-23 12:01 ` Sudeep Holla
2026-09-23 12:55 ` Uwe Kleine-König
2026-09-23 14:25 ` Sudeep Holla
2026-09-23 14:51 ` Hans de Goede
2026-09-23 15:42 ` Hans de Goede [this message]
2026-09-18 9:29 ` [PATCH v7 2/2] firmware: arm_scmi: Always create devices for standard protocols Hans de Goede
2026-09-25 9:37 ` [PATCH v7 0/2] firmware: arm_scmi: fix module auto-loading Sudeep Holla
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=839b884b-9db0-4215-9715-40549d1c6a26@oss.qualcomm.com \
--to=johannes.goede@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=andersson@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=cristian.marussi@arm.com \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=u.kleine-koenig@baylibre.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