mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zihuan Zhang <zhangzihuan@kylinos.cn>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J . wysocki" <rafael@kernel.org>,
	zhenglifeng <zhenglifeng1@huawei.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] cpufreq: sh: drop redundant freq_table argument
Date: Tue, 2 Sep 2025 14:43:14 +0800	[thread overview]
Message-ID: <124d4b02-5268-4919-aba8-eab7945fff28@kylinos.cn> (raw)
In-Reply-To: <20250902062349.cxg5377chzqtb76r@vireshk-i7>


在 2025/9/2 14:23, Viresh Kumar 写道:
> On 02-09-25, 14:06, Zihuan Zhang wrote:
>> I also noticed that in some drivers like acpi-cpufreq.c, if freq_table
>> allocation fails, the driver won’t be registered at all.
>>
>> In such cases,
>>
>> should the NULL check be done inside the core helper functions, or should it
>> be left to the drivers?
> Not all drivers need a freq-table and so it is fine for them to not
> have one. This driver looks like can work without a freq table too.
>
Understood, Thanks!

  reply	other threads:[~2025-09-02  6:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 11:25 [PATCH v1 0/3] cpufreq: drop redundant freq_table argument in helpers Zihuan Zhang
2025-09-01 11:25 ` [PATCH v1 1/3] cpufreq: Drop redundant freq_table parameter Zihuan Zhang
2025-09-01 11:25 ` [PATCH v1 2/3] cpufreq: sh: drop redundant freq_table argument Zihuan Zhang
2025-09-02  5:40   ` Viresh Kumar
2025-09-02  6:06     ` Zihuan Zhang
2025-09-02  6:23       ` Viresh Kumar
2025-09-02  6:43         ` Zihuan Zhang [this message]
2025-09-01 11:25 ` [PATCH v1 3/3] cpufreq: virtual: " Zihuan Zhang
2025-09-02  5:42 ` [PATCH v1 0/3] cpufreq: drop redundant freq_table argument in helpers Viresh Kumar
2025-09-02  5:54   ` Zihuan Zhang

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=124d4b02-5268-4919-aba8-eab7945fff28@kylinos.cn \
    --to=zhangzihuan@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=zhenglifeng1@huawei.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

all inboxes | Powered by JetHome®