mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Roberto Ricci <io@r-ricci.it>, Thomas Renninger <trenn@suse.com>,
	Shuah Khan <shuah@kernel.org>,
	"John B. Wyatt IV" <jwyatt@redhat.com>,
	John Kacur <jkacur@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v5 0/4] cpupower: fix various man pages issues
Date: Wed, 25 Mar 2026 13:39:44 -0600	[thread overview]
Message-ID: <598409fd-73d3-473a-9e1c-65f47ef9d06b@linuxfoundation.org> (raw)
In-Reply-To: <20260324223921.14317-1-io@r-ricci.it>

On 3/24/26 16:39, Roberto Ricci wrote:
> This patch series fixes a few issues with the cpupower manual pages,
> such as missing or incorrect options and trailing whitespace.
> 
> Signed-off-by: Roberto Ricci <io@r-ricci.it>
> 
> ---
> Changes in v5:
> - Drop whitespace removal patches
>    Link to v4: https://lore.kernel.org/linux-pm/20260324013543.4776-1-io@r-ricci.it/
> 

Applied to my cpupower branch - I will send this my next pr to
PM maintainer.

https://web.git.kernel.org/pub/scm/linux/kernel/git/shuah/linux.git/log/?h=cpupower

thanks,
-- Shuah

      parent reply	other threads:[~2026-03-25 19:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-24 22:39 Roberto Ricci
2026-03-24 22:39 ` [PATCH v5 1/4] cpupower-idle-info.1: fix short option names Roberto Ricci
2026-03-24 22:39 ` [PATCH v5 2/4] cpupower-frequency-info.1: use the proper name of the --perf option Roberto Ricci
2026-03-24 23:06   ` Shuah Khan
2026-03-24 23:11     ` Shuah Khan
2026-03-25 11:25     ` Roberto Ricci
2026-03-24 22:39 ` [PATCH v5 3/4] cpupower-frequency-info.1: document --boost and --epp options Roberto Ricci
2026-03-24 22:39 ` [PATCH v5 4/4] cpupower-info.1: describe the --perf-bias option Roberto Ricci
2026-03-25 19:39 ` 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=598409fd-73d3-473a-9e1c-65f47ef9d06b@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=io@r-ricci.it \
    --cc=jkacur@redhat.com \
    --cc=jwyatt@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=shuah@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

Powered by JetHome