From: Viresh Kumar <viresh.kumar@linaro.org>
To: Lizhe <sensor1010@163.com>
Cc: rafael@kernel.org, axun.yang@flygoat.com,
linux-pm@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Remove redundant exit() functions
Date: Fri, 12 Apr 2024 11:22:17 +0530 [thread overview]
Message-ID: <20240412055217.soyzvivcenoadt3m@vireshk-i7> (raw)
In-Reply-To: <20240409141909.4413-1-sensor1010@163.com>
On 09-04-24, 07:19, Lizhe wrote:
> The return value of exit() is 0 and it performs no action.
> This function can be omitted. Please refer to the end condition
> check in the __cpufreq_offline() function.
>
> Signed-off-by: Lizhe <sensor1010@163.com>
> ---
> drivers/cpufreq/cpufreq-nforce2.c | 6 ------
> drivers/cpufreq/loongson2_cpufreq.c | 6 ------
> 2 files changed, 12 deletions(-)
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2024-04-12 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 14:19 [PATCH] cpufreq: Remove redundant exit() functions Lizhe
2024-04-12 5:52 ` Viresh Kumar [this message]
[not found] ` <1355118777.446339.1712756972631.JavaMail.root@mail-tracker-145-3ep34-c9h23-5f64cf7787-82gdh>
2024-04-12 5:53 ` 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=20240412055217.soyzvivcenoadt3m@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=axun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sensor1010@163.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;
as well as URLs for NNTP newsgroup(s).