From: "tip-bot for zhenwei.pi" <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: tglx@linutronix.de, peterz@infradead.org,
zhenwei.pi@youruncloud.com, hpa@zytor.com,
torvalds@linux-foundation.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: [tip:x86/boot] x86/kconfig: Remove residual "no-hlt" boot parameter reference
Date: Mon, 8 Jan 2018 12:35:43 -0800 [thread overview]
Message-ID: <tip-9e7a0bc0a315f3c2a6902e04b60a86edd78c1164@git.kernel.org> (raw)
In-Reply-To: <1514170591-25120-1-git-send-email-zhenwei.pi@youruncloud.com>
Commit-ID: 9e7a0bc0a315f3c2a6902e04b60a86edd78c1164
Gitweb: https://git.kernel.org/tip/9e7a0bc0a315f3c2a6902e04b60a86edd78c1164
Author: zhenwei.pi <zhenwei.pi@youruncloud.com>
AuthorDate: Mon, 25 Dec 2017 10:56:31 +0800
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Mon, 8 Jan 2018 20:09:25 +0100
x86/kconfig: Remove residual "no-hlt" boot parameter reference
The "no-hlt" boot parameter has been removed ~5 years ago:
27be45700021 ("x86 idle: remove 32-bit-only "no-hlt" parameter, hlt_works_ok flag")
Remove a stale reference from the documentation as well.
Signed-off-by: zhenwei.pi <zhenwei.pi@youruncloud.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1514170591-25120-1-git-send-email-zhenwei.pi@youruncloud.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
arch/x86/Kconfig | 21 ++++++++++-----------
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 8eed3f9..cf49280 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -2425,19 +2425,18 @@ menuconfig APM
1) make sure that you have enough swap space and that it is
enabled.
- 2) pass the "no-hlt" option to the kernel
- 3) switch on floating point emulation in the kernel and pass
+ 2) switch on floating point emulation in the kernel and pass
the "no387" option to the kernel
- 4) pass the "floppy=nodma" option to the kernel
- 5) pass the "mem=4M" option to the kernel (thereby disabling
+ 3) pass the "floppy=nodma" option to the kernel
+ 4) pass the "mem=4M" option to the kernel (thereby disabling
all but the first 4 MB of RAM)
- 6) make sure that the CPU is not over clocked.
- 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
- 8) disable the cache from your BIOS settings
- 9) install a fan for the video card or exchange video RAM
- 10) install a better fan for the CPU
- 11) exchange RAM chips
- 12) exchange the motherboard.
+ 5) make sure that the CPU is not over clocked.
+ 6) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
+ 7) disable the cache from your BIOS settings
+ 8) install a fan for the video card or exchange video RAM
+ 9) install a better fan for the CPU
+ 10) exchange RAM chips
+ 11) exchange the motherboard.
To compile this driver as a module, choose M here: the
module will be called apm.
prev parent reply other threads:[~2018-01-08 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 2:56 [PATCH] x86/kconfig: remove residual cmdline param "no-hlt" zhenwei.pi
2018-01-08 20:35 ` tip-bot for zhenwei.pi [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=tip-9e7a0bc0a315f3c2a6902e04b60a86edd78c1164@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=zhenwei.pi@youruncloud.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