From: Greg KH <gregkh@linuxfoundation.org>
To: lizhe <sensor1010@163.com>
Cc: "viresh.kumar" <viresh.kumar@linaro.org>,
"grygorii.strashko" <grygorii.strashko@ti.com>,
"gregory.clement" <gregory.clement@bootlin.com>,
"grant.likely" <grant.likely@secretlab.ca>,
bsegall <bsegall@google.com>, broonie <broonie@kernel.org>,
bristot <bristot@redhat.com>, brgl <brgl@bgdev.pl>,
"f.fainelli" <f.fainelli@gmail.com>,
"fancer.lancer" <fancer.lancer@gmail.com>,
festevam <festevam@gmail.com>, Finn Thain <fthain@linux-m68k.org>,
rafael <rafael@kernel.org>, linux-pm <linux-pm@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: exit() callback is optional
Date: Fri, 12 Apr 2024 11:14:49 +0200 [thread overview]
Message-ID: <2024041238-publisher-provable-7ebe@gregkh> (raw)
In-Reply-To: <663acff5.349d4.18ed18da6ff.Coremail.sensor1010@163.com>
On Fri, Apr 12, 2024 at 05:05:05PM +0800, lizhe wrote:
> I found it first and submitted it to the main line first. Please be fair and just. Let him withdraw his patch.
lore.kernel.org links for this please?
next prev parent reply other threads:[~2024-04-12 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 5:49 [PATCH] cpufreq: exit() callback is optional Viresh Kumar
[not found] ` <5759bc29.32d04.18ed0ef5037.Coremail.sensor1010@163.com>
2024-04-12 6:24 ` Viresh Kumar
[not found] ` <1b53a162.32e95.18ed0fdb13e.Coremail.sensor1010@163.com>
2024-04-12 6:32 ` Viresh Kumar
[not found] ` <2117690204.533771.1712904398042.JavaMail.root@mail-tracker-145-3ep34-c9h23-5f64cf7787-82gdh>
2024-04-12 7:57 ` Greg KH
[not found] ` <663acff5.349d4.18ed18da6ff.Coremail.sensor1010@163.com>
2024-04-12 9:14 ` Greg KH [this message]
2024-04-12 9:23 ` Viresh Kumar
2024-04-12 9:21 ` Viresh Kumar
2024-04-12 10:28 ` Greg KH
[not found] ` <28e13fe5.bc4.18ed2962985.Coremail.sensor1010@163.com>
2024-04-12 14:31 ` lizhe
2024-04-12 14:41 ` lizhe
2024-04-22 11:21 ` shuah
[not found] ` <5c601757.54f80.18f05956113.Coremail.sensor1010@163.com>
2024-05-03 21:30 ` Shuah Khan
[not found] ` <7bd5d6c1.32db8.18ed0f5e6c3.Coremail.sensor1010@163.com>
2024-04-12 6:27 ` Viresh Kumar
2024-04-12 11:08 ` Rafael J. Wysocki
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=2024041238-publisher-provable-7ebe@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=brgl@bgdev.pl \
--cc=bristot@redhat.com \
--cc=broonie@kernel.org \
--cc=bsegall@google.com \
--cc=f.fainelli@gmail.com \
--cc=fancer.lancer@gmail.com \
--cc=festevam@gmail.com \
--cc=fthain@linux-m68k.org \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@bootlin.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sensor1010@163.com \
--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