From: Randy Dunlap <randy.dunlap@oracle.com>
To: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Cc: Len Brown <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: [PATCH] DOC: fix acpi kernel-parameters
Date: Fri, 21 Nov 2008 13:57:22 -0800 [thread overview]
Message-ID: <49272EC2.5080600@oracle.com> (raw)
Please queue after one of Rafael's patches. This does not
apply cleanly to Linus-mainline, but it does apply to
linux-next or -mm.
From: Randy Dunlap <randy.dunlap@oracle.com>
Spell out "wrt". I suspect plenty of people won't know
what that means.
Fix a '}' that should be a ']'.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
Documentation/kernel-parameters.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--- linux-next-20081112.orig/Documentation/kernel-parameters.txt
+++ linux-next-20081112/Documentation/kernel-parameters.txt
@@ -158,9 +158,9 @@ and is between 256 and 4096 characters.
s4_nohwsig prevents ACPI hardware signature from being
used during resume from hibernation.
old_ordering causes the ACPI 1.0 ordering of the _PTS
- control method, wrt putting devices into low power
- states, to be enforced (the ACPI 2.0 ordering of _PTS is
- used by default).
+ control method, with respect to putting devices into
+ low power states, to be enforced (the ACPI 2.0 ordering
+ of _PTS is used by default).
s4_nonvs prevents the kernel from saving/restoring the
ACPI NVS memory during hibernation.
@@ -197,7 +197,7 @@ and is between 256 and 4096 characters.
acpi_skip_timer_override [HW,ACPI]
Recognize and ignore IRQ0/pin2 Interrupt Override.
For broken nForce2 BIOS resulting in XT-PIC timer.
- acpi_use_timer_override [HW,ACPI}
+ acpi_use_timer_override [HW,ACPI]
Use timer override. For some broken Nvidia NF5 boards
that require a timer override, but don't have
HPET
reply other threads:[~2008-11-21 21:59 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=49272EC2.5080600@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=rjw@sisk.pl \
/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