From: Borislav Petkov <bp@amd64.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Borislav Petkov <borislav.petkov@amd.com>,
Thomas Renninger <trenn@suse.de>,
"H. Peter Anvin" <hpa@linux.intel.com>,
linux-acpi@vger.kernel.org
Subject: [PATCH] ACPI: Sanitize ACPI_INITRD_TABLE_OVERRIDE Kconfig text
Date: Thu, 4 Oct 2012 11:02:34 +0200 [thread overview]
Message-ID: <1349341354-21466-1-git-send-email-bp@amd64.org> (raw)
From: Borislav Petkov <borislav.petkov@amd.com>
Make the bool prompt text shorter and fit the style of Kconfig options
and move the actual description into the help text.
No functionality change.
Cc: Thomas Renninger <trenn@suse.de>
Cc: H. Peter Anvin <hpa@linux.intel.com>
Cc: linux-acpi@vger.kernel.org
Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
---
I guess this one is against tip's x86/acpi branch.
drivers/acpi/Kconfig | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
index 44cea5d4b04e..c556b794e12f 100644
--- a/drivers/acpi/Kconfig
+++ b/drivers/acpi/Kconfig
@@ -262,13 +262,13 @@ config ACPI_CUSTOM_DSDT
default ACPI_CUSTOM_DSDT_FILE != ""
config ACPI_INITRD_TABLE_OVERRIDE
- bool "ACPI tables can be passed via uncompressed cpio in initrd"
+ bool "ACPI tables override via initrd"
default n
help
This option provides functionality to override arbitrary ACPI tables
- via initrd. No functional change if no ACPI tables are passed via
- initrd, therefore it's safe to say Y.
- See Documentation/acpi/initrd_table_override.txt for details
+ via uncompressed cpio in initrd. No functional change if no ACPI
+ tables are passed via the initrd, therefore it's safe to say Y.
+ See Documentation/acpi/initrd_table_override.txt for details.
config ACPI_BLACKLIST_YEAR
int "Disable ACPI for systems before Jan 1st this year" if X86_32
--
1.7.11.rc1
reply other threads:[~2012-10-04 9:02 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=1349341354-21466-1-git-send-email-bp@amd64.org \
--to=bp@amd64.org \
--cc=borislav.petkov@amd.com \
--cc=hpa@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).