From: Wen Pu <puwen@hygon.cn>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"bp@alien8.de" <bp@alien8.de>,
"victording@google.com" <victording@google.com>,
"kim.phillips@amd.com" <kim.phillips@amd.com>,
"rui.zhang@intel.com" <rui.zhang@intel.com>
Subject: Re: [RFC PATCH] powercap: Add Hygon Fam18h RAPL support
Date: Tue, 2 Mar 2021 02:04:53 +0000 [thread overview]
Message-ID: <0994b1d7-3439-b513-7a87-c1463e04d311@hygon.cn> (raw)
In-Reply-To: <CAJZ5v0jyHywkUhF87sNHXMtG=QBmO23LwAFW0aHQMJsFSr1y+g@mail.gmail.com>
On 2021/3/1 22:20, Rafael J. Wysocki wrote:
> On Mon, Mar 1, 2021 at 3:18 AM Wen Pu <puwen@hygon.cn> wrote:
>>
>> On 2021/2/28 23:42, Srinivas Pandruvada wrote:
>>> On Thu, 2021-02-25 at 21:01 +0800, Pu Wen wrote:
>>>> Enable Hygon Fam18h RAPL support for the power capping framework.
>>>>
>>> If this patch is tested and works on this processor, not sure why this
>>> is RFC?
>>
>> This patch is tested and works on Hygon processor. The 'RFC' is automated
>> generated by my script ;)
>
> Well, care to resend as non-RFC, then?
OK, already resend. Thanks!
--
Regards,
Pu Wen
prev parent reply other threads:[~2021-03-02 7:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 13:01 [RFC PATCH] powercap: Add Hygon Fam18h RAPL support Pu Wen
2021-02-28 15:42 ` Srinivas Pandruvada
2021-03-01 2:16 ` Wen Pu
2021-03-01 14:20 ` Rafael J. Wysocki
2021-03-02 2:04 ` Wen Pu [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=0994b1d7-3439-b513-7a87-c1463e04d311@hygon.cn \
--to=puwen@hygon.cn \
--cc=bp@alien8.de \
--cc=kim.phillips@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=victording@google.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).