linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: shuah <shuah@kernel.org>
To: latha@linux.vnet.ibm.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: trenn@suse.com, shuah <shuah@kernel.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: [PATCH] Correction to manpage of cpupower
Date: Mon, 27 Jan 2020 08:49:58 -0700	[thread overview]
Message-ID: <6971ef88-7187-94d4-1693-45f6e57040ff@kernel.org> (raw)
In-Reply-To: <20200123143319.19580-1-latha@linux.vnet.ibm.com>

On 1/23/20 7:33 AM, latha@linux.vnet.ibm.com wrote:
> From: Brahadambal Srinivasan <latha@linux.vnet.ibm.com>
> 
> Manpage of cpupower is listing wrong sub-commands in "See Also"
> section. The option for cpupower-idle(1) should actually be
> cpupower-idle-info(1) and cpupower-idle-set(1). This patch corrects
> this anomaly.
> 
> Signed-off-by: Brahadambal Srinivasan <latha@linux.vnet.ibm.com>
> ---
>   tools/power/cpupower/man/cpupower.1 | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/tools/power/cpupower/man/cpupower.1 b/tools/power/cpupower/man/cpupower.1
> index baf741d06e82..bdbf089794c7 100644
> --- a/tools/power/cpupower/man/cpupower.1
> +++ b/tools/power/cpupower/man/cpupower.1
> @@ -62,9 +62,9 @@ all cores
>   Print the package name and version number.
>   
>   .SH "SEE ALSO"
> -cpupower-set(1), cpupower-info(1), cpupower-idle(1),
> -cpupower-frequency-set(1), cpupower-frequency-info(1), cpupower-monitor(1),
> -powertop(1)
> +cpupower-set(1), cpupower-info(1), cpupower-idle-info(1),
> +cpupower-idle-set(1), cpupower-frequency-set(1), cpupower-frequency-info(1),
> +cpupower-monitor(1), powertop(1)
>   .PP
>   .SH AUTHORS
>   .nf
> 

Thanks for fixing this. Applied to

git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git cpupower

for 5.6-rc1 or rc2 pull request to pm maintainer Rafael Wysocki

Please remember to run checkpatch before sending patches in the future
I fixed up minor white space errors in this patch before applying it.

Please run get_maintainers as well to get the complete list of
recipients in the future.

thanks,
-- Shuah

      reply	other threads:[~2020-01-27 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 14:33 [PATCH] Correction to manpage of cpupower latha
2020-01-27 15:49 ` shuah [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=6971ef88-7187-94d4-1693-45f6e57040ff@kernel.org \
    --to=shuah@kernel.org \
    --cc=latha@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.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).