linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Tor Vic <torvic9@mailbox.org>, trenn@suse.com, shuah@kernel.org
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] tools/power/cpupower: Add documentation for some recently introduced options
Date: Mon, 30 Sep 2024 09:51:06 -0600	[thread overview]
Message-ID: <73b9ad39-cf4a-4030-83fc-4e632177b7a3@linuxfoundation.org> (raw)
In-Reply-To: <ba84bf50-67fa-44b2-b73c-f219c277e38f@linuxfoundation.org>

On 9/24/24 12:36, Shuah Khan wrote:
> On 9/24/24 08:17, Tor Vic wrote:
>> The 'cpupower-set' tool has learned new options with commits:
>>
>>    f2ab5557119a "cpupower: Add EPP value change support"
>>    df8776b03689 "cpupower: Add support for amd_pstate mode change"
>>    eb426fc6bdd6 "cpupower: Add turbo-boost support in cpupower"
> 
> 
> Thank you for finding and fixing this.
> 
> Checkpatch complains about commit description format. I fixed them
> for now.
> 
> This patch will be applied once the merge window closes.
> 
>>
>> However, the corresponding manpage was never updated.
> 
> Thank you for finding and fixing this.
> 
> This patch will be applied once the merge window closes.
>>
>> Add a basic description of these new options to the existing manpage.
>>
>> Signed-off-by: Tor Vic <torvic9@mailbox.org>
>> ---
> 

Thank you. Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git/log/?h=cpupower

It will be included in my next pull request to PM maintainer.

thanks,
-- Shuah


      reply	other threads:[~2024-09-30 15:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 14:17 [PATCH] tools/power/cpupower: Add documentation for some recently introduced options Tor Vic
2024-09-24 18:36 ` Shuah Khan
2024-09-30 15:51   ` Shuah Khan [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=73b9ad39-cf4a-4030-83fc-4e632177b7a3@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=torvic9@mailbox.org \
    --cc=trenn@suse.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).