From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ACPI / ARM64: Don't enable ACPI by default on ARM64
Date: Fri, 15 Apr 2016 08:53:41 +0100 [thread overview]
Message-ID: <1460706823-16566-1-git-send-email-broonie@kernel.org> (raw)
If ACPI is selectable it is enabled by default. This is a good choice
for architectures where the overwhelming majority of systems use ACPI
like x86 and IA-64 but is less clear for architectures where it's less
common like ARM64. Change the default selection so that it's only done
explicitly on those architectures where ACPI is universally used.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
drivers/acpi/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
index 82b96ee8624c..2fcf87a6d270 100644
--- a/drivers/acpi/Kconfig
+++ b/drivers/acpi/Kconfig
@@ -8,7 +8,7 @@ menuconfig ACPI
depends on IA64 || X86 || (ARM64 && EXPERT)
depends on PCI
select PNP
- default y
+ default y if (IA64 || X86)
help
Advanced Configuration and Power Interface (ACPI) support for
Linux requires an ACPI-compliant platform (hardware/firmware),
--
2.8.0.rc3
next reply other threads:[~2016-04-15 7:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 7:53 Mark Brown [this message]
2016-04-15 7:53 ` [PATCH 2/3] ACPI / ARM64: Remove EXPERT dependency for ACPI on ARM64 Mark Brown
2016-04-15 16:19 ` Roy Franz (HPE)
2016-04-15 17:48 ` Olof Johansson
2016-04-20 16:30 ` Timur Tabi
2016-04-15 7:53 ` [PATCH 3/3] arm64: defconfig: Enable ACPI Mark Brown
2016-04-15 8:42 ` Catalin Marinas
2016-04-15 9:04 ` Hanjun Guo
2016-04-15 16:17 ` Roy Franz (HPE)
2016-04-15 8:42 ` [PATCH 1/3] ACPI / ARM64: Don't enable ACPI by default on ARM64 Catalin Marinas
2016-04-15 9:03 ` Hanjun Guo
2016-04-15 17:48 ` Olof Johansson
2016-04-16 15:11 ` Sergei Shtylyov
2016-04-21 0:10 ` Rafael J. Wysocki
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=1460706823-16566-1-git-send-email-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).