From: Amerigo Wang <amwang@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: len.brown@intel.com, WANG Cong <amwang@redhat.com>,
Randy Dunlap <rdunlap@xenotime.net> (maintainer:DOCUMENTATION),
linux-doc@vger.kernel.org (open list:DOCUMENTATION)
Subject: [Patch] kernel doc: fix some ACPI documentation
Date: Wed, 19 Jan 2011 13:41:58 +0800 [thread overview]
Message-ID: <1295415718-16541-1-git-send-email-amwang@redhat.com> (raw)
In Documentation/kernel-parameters.txt, apparently 0xffffffff should
be acpi.debug_layer not acpi.debug_level.
In Documentation/acpi/debug.txt, component ACPI_NUMA is missing, add it.
Signed-off-by: WANG Cong <amwang@redhat.com>
---
diff --git a/Documentation/acpi/debug.txt b/Documentation/acpi/debug.txt
index 65bf47c..1af2a01 100644
--- a/Documentation/acpi/debug.txt
+++ b/Documentation/acpi/debug.txt
@@ -63,6 +63,7 @@ shows the supported mask values, currently these:
ACPI_MEMORY_DEVICE_COMPONENT 0x08000000
ACPI_VIDEO_COMPONENT 0x10000000
ACPI_PROCESSOR_COMPONENT 0x20000000
+ ACPI_NUMA 0x80000000
debug_level
-----------
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index b72e071..75f2334 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -193,7 +193,7 @@ and is between 256 and 4096 characters. It is defined in the file
object while interpreting AML:
acpi.debug_layer=0xffffffff acpi.debug_level=0x2
Enable all messages related to ACPI hardware:
- acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
+ acpi.debug_layer=0xffffffff acpi.debug_level=0x2
Some values produce so much output that the system is
unusable. The "log_buf_len" parameter may be useful
reply other threads:[~2011-01-19 5:42 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=1295415718-16541-1-git-send-email-amwang@redhat.com \
--to=amwang@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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
all inboxes | Powered by JetHome®