From: Viresh Kumar <viresh.kumar@linaro.org>
To: lizhe <sensor1010@163.com>
Cc: christophe.leroy@csgroup.eu, naveen.n.rao@linux.ibm.com,
axun.yang@flygoat.com, rafael@kernel.org,
linux-pm@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Remove redundant exit() functions
Date: Fri, 12 Apr 2024 11:23:03 +0530 [thread overview]
Message-ID: <20240412055303.p32ssort5ir5yq3q@vireshk-i7> (raw)
In-Reply-To: <1355118777.446339.1712756972631.JavaMail.root@mail-tracker-145-3ep34-c9h23-5f64cf7787-82gdh>
On 10-04-24, 21:49, lizhe wrote:
>
>
>
> Hi,
> I have already tested it, it is functioning properly, Please review.
Please don't expect reply within a day from maintainers. Give at least two weeks
before posting another email to remind people.
--
viresh
prev parent reply other threads:[~2024-04-12 5:53 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
[not found] ` <1355118777.446339.1712756972631.JavaMail.root@mail-tracker-145-3ep34-c9h23-5f64cf7787-82gdh>
2024-04-12 5:53 ` Viresh Kumar [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=20240412055303.p32ssort5ir5yq3q@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=axun.yang@flygoat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).