From: Xin Hao <xhao@linux.alibaba.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] cpufreq: CPPC: simply the code access 'highest_perf' value in cppc_perf_caps struct
Date: Tue, 4 Aug 2020 12:47:37 +0800 [thread overview]
Message-ID: <5f1f469d-4920-2d57-cb7c-0fea45e837c2@linux.alibaba.com> (raw)
In-Reply-To: <20200804043740.cde3ij2uk4xczemh@vireshk-mac-ubuntu>
Thanks
在 2020/8/4 下午12:37, Viresh Kumar 写道:
> On 04-08-20, 10:37, Xin Hao wrote:
>> Hi everyone:
>>
>> I want to know why my patch didn't merge into upstream ?
> I have sent a pull request earlier today to Rafael and this will get
> merged in the next pull request Rafael will send to Linus.
>
prev parent reply other threads:[~2020-08-04 4:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 4:20 [PATCH v3] cpufreq: CPPC: simply the code access 'highest_perf' value in cppc_perf_caps struct Xin Hao
2020-07-01 4:52 ` Viresh Kumar
2020-07-01 12:16 ` Rafael J. Wysocki
2020-07-02 2:37 ` Viresh Kumar
2020-07-02 11:06 ` Rafael J. Wysocki
2020-07-02 11:09 ` Viresh Kumar
2020-08-04 2:37 ` Xin Hao
2020-08-04 4:37 ` Viresh Kumar
2020-08-04 4:47 ` Xin Hao [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=5f1f469d-4920-2d57-cb7c-0fea45e837c2@linux.alibaba.com \
--to=xhao@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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).