From: "Rafael J. Wysocki" <rafael@kernel.org>
To: "Pali Rohár" <pali@kernel.org>, "Viresh Kumar" <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/9] cpufreq: Add missing modalias for tristate drivers
Date: Mon, 9 Nov 2020 15:18:03 +0100 [thread overview]
Message-ID: <CAJZ5v0gxRHUt7dij7zFomXxmCEPVxiTEv+qu8kZESbsE3A+bBQ@mail.gmail.com> (raw)
In-Reply-To: <20201103151139.29690-1-pali@kernel.org>
On Tue, Nov 3, 2020 at 4:14 PM Pali Rohár <pali@kernel.org> wrote:
>
> Some of cpufreq drivers are tristate, can be compiled as modules, but do
> not have defined modalias for automatic loading. This patch series add
> for all those cpufreq drivers missing MODULE_DEVICE_TABLE macro, based
> on OF definitions, or MODULE_ALIAS for platform drivers.
>
> MODULE_DEVICE_TABLE is not explictily added only for speedstep-centrino,
> speedstep-ich and speedstep-smi drivers as it was removed in commit
> b11d77fa300d9 ("cpufreq: Convert to new X86 CPU match macros").
>
> Pali Rohár (9):
> cpufreq: ap806: Add missing MODULE_DEVICE_TABLE
> cpufreq: highbank: Add missing MODULE_DEVICE_TABLE
> cpufreq: mediatek: Add missing MODULE_DEVICE_TABLE
> cpufreq: qcom: Add missing MODULE_DEVICE_TABLE
> cpufreq: st: Add missing MODULE_DEVICE_TABLE
> cpufreq: sun50i: Add missing MODULE_DEVICE_TABLE
> cpufreq: loongson1: Add missing MODULE_ALIAS
> cpufreq: scpi: Add missing MODULE_ALIAS
> cpufreq: vexpress-spc: Add missing MODULE_ALIAS
>
> drivers/cpufreq/armada-8k-cpufreq.c | 6 ++++++
> drivers/cpufreq/highbank-cpufreq.c | 7 +++++++
> drivers/cpufreq/loongson1-cpufreq.c | 1 +
> drivers/cpufreq/mediatek-cpufreq.c | 1 +
> drivers/cpufreq/qcom-cpufreq-nvmem.c | 1 +
> drivers/cpufreq/scpi-cpufreq.c | 1 +
> drivers/cpufreq/sti-cpufreq.c | 7 +++++++
> drivers/cpufreq/sun50i-cpufreq-nvmem.c | 1 +
> drivers/cpufreq/vexpress-spc-cpufreq.c | 1 +
> 9 files changed, 26 insertions(+)
>
> --
Viresh, any comments?
next prev parent reply other threads:[~2020-11-09 14:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 15:11 [PATCH 0/9] cpufreq: Add missing modalias for tristate drivers Pali Rohár
2020-11-03 15:11 ` [PATCH 1/9] cpufreq: ap806: Add missing MODULE_DEVICE_TABLE Pali Rohár
2020-11-03 15:11 ` [PATCH 2/9] cpufreq: highbank: " Pali Rohár
2020-11-03 15:11 ` [PATCH 3/9] cpufreq: mediatek: " Pali Rohár
2020-11-03 15:11 ` [PATCH 4/9] cpufreq: qcom: " Pali Rohár
2020-11-03 15:11 ` [PATCH 5/9] cpufreq: st: " Pali Rohár
2020-11-03 15:11 ` [PATCH 6/9] cpufreq: sun50i: " Pali Rohár
2020-11-10 2:41 ` Frank Lee
2020-11-03 15:11 ` [PATCH 7/9] cpufreq: loongson1: Add missing MODULE_ALIAS Pali Rohár
2020-11-03 15:11 ` [PATCH 8/9] cpufreq: scpi: " Pali Rohár
2020-11-03 15:11 ` [PATCH 9/9] cpufreq: vexpress-spc: " Pali Rohár
2020-11-09 14:18 ` Rafael J. Wysocki [this message]
2020-11-10 2:35 ` [PATCH 0/9] cpufreq: Add missing modalias for tristate drivers Viresh Kumar
2020-11-10 12:39 ` Rafael J. Wysocki
2020-11-11 6:01 ` Viresh Kumar
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=CAJZ5v0gxRHUt7dij7zFomXxmCEPVxiTEv+qu8kZESbsE3A+bBQ@mail.gmail.com \
--to=rafael@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).