From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Petr Mladek <pmladek@suse.com>,
Wardenjohn <zhangwarden@gmail.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Leonardo Bras <leobras@redhat.com>,
John Ogness <john.ogness@linutronix.de>,
Bo Liu <liubo03@inspur.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH] kernel: Fix "select" wording on HZ_250 description
Date: Mon, 3 Feb 2025 09:50:00 +0700 [thread overview]
Message-ID: <20250203025000.17953-1-bagasdotme@gmail.com> (raw)
HZ_250 config description contains alternative choice for NTSC
media users (HZ_300), which is written as "selected 300Hz". This is
incorrect, as it implies that HZ_300 is automatically selected
whereas the user has chosen HZ_250 instead.
Fix the wording to "select 300Hz".
Fixes: 40fcfc87222e ("[PATCH] HZ: 300Hz support")
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
---
kernel/Kconfig.hz | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/Kconfig.hz b/kernel/Kconfig.hz
index 38ef6d06888ef1..ce1435cb08b1ec 100644
--- a/kernel/Kconfig.hz
+++ b/kernel/Kconfig.hz
@@ -30,7 +30,7 @@ choice
250 Hz is a good compromise choice allowing server performance
while also showing good interactive responsiveness even
on SMP and NUMA systems. If you are going to be using NTSC video
- or multimedia, selected 300Hz instead.
+ or multimedia, select 300Hz instead.
config HZ_300
bool "300 HZ"
base-commit: 2014c95afecee3e76ca4a56956a936e23283f05b
--
An old man doll... just what I always wanted! - Clara
reply other threads:[~2025-02-03 2:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250203025000.17953-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liubo03@inspur.com \
--cc=palmer@rivosinc.com \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=zhangwarden@gmail.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