From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Shuah Khan <skhan@linuxfoundation.org>,
linux-doc@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v2] docs: kernel-parameters: add CPU_FREQ, CPU_IDLE build options
Date: Mon, 24 Aug 2026 11:09:03 -0600 [thread overview]
Message-ID: <87tsojxx74.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20260815172934.3604009-1-rdunlap@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> CPU_FREQ and CPU_IDLE are used in descriptions of some kernel parameters
> so add their descriptions to the build options list.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> v2: wordsmithing by Rafael (thanks)
>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Shuah Khan <skhan@linuxfoundation.org>
> Cc: linux-doc@vger.kernel.org
> Cc: "Rafael J. Wysocki" <rafael@kernel.org>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: Daniel Lezcano <daniel.lezcano@kernel.org>
> Cc: linux-pm@vger.kernel.org
>
> Documentation/admin-guide/kernel-parameters.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-next-20260814.orig/Documentation/admin-guide/kernel-parameters.txt
> +++ linux-next-20260814/Documentation/admin-guide/kernel-parameters.txt
> @@ -8,6 +8,8 @@
> ARM64 ARM64 architecture is enabled.
> CLK Common clock infrastructure is enabled.
> CMA Contiguous Memory Area support is enabled.
> + CPU_FREQ CPU frequency scaling is enabled.
> + CPU_IDLE CPU idle time management is enabled.
> DRM Direct Rendering Management support is enabled.
Applied, thanks.
jon
prev parent reply other threads:[~2026-08-24 17:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 17:29 [PATCH v2] docs: kernel-parameters: add CPU_FREQ, CPU_IDLE build options Randy Dunlap
2026-08-15 18:16 ` Rafael J. Wysocki (Intel)
2026-08-24 17:09 ` Jonathan Corbet [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=87tsojxx74.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=daniel.lezcano@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--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