From: Hugh Dickins <hugh@veritas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Len Brown <len.brown@intel.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH] reverse CONFIG_ACPI_PROC_EVENT default
Date: Mon, 27 Aug 2007 16:04:39 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708271602170.21853@blonde.wat.veritas.com> (raw)
Sigh. Again an ACPI assault on the Thinkpad's Fn+F4 to suspend to RAM.
The default and text for CONFIG_THINKPAD_ACPI_INPUT_ENABLED were fixed
in -rc3, but now 14e04fb34ffa82ee61ae69f98d8fca12d2e8e31c introduces
CONFIG_ACPI_PROC_EVENT default n to disable it again. Change default
to y, and add comment to make it clearer that n is for future distros.
Signed-off-by: Hugh Dickins <hugh@veritas.com>
--- 2.6.23-rc3-git10/drivers/acpi/Kconfig 2007-08-26 18:10:15.000000000 +0100
+++ linux/drivers/acpi/Kconfig 2007-08-26 18:59:16.000000000 +0100
@@ -71,6 +71,7 @@ config ACPI_PROCFS
config ACPI_PROC_EVENT
bool "Deprecated /proc/acpi/event support"
depends on PROC_FS
+ default y
---help---
A user-space daemon, acpi, typically read /proc/acpi/event
and handled all ACPI sub-system generated events.
@@ -78,10 +79,13 @@ config ACPI_PROC_EVENT
These events are now delivered to user-space via
either the input layer, or as netlink events.
- This build option enables the old code for for legacy
+ This build option enables the old code for legacy
user-space implementation. After some time, this will
be moved under CONFIG_ACPI_PROCFS, and then deleted.
+ Say Y here to retain the old behaviour. Say N if your
+ user-space is newer than kernel 2.6.23 (September 2007).
+
config ACPI_AC
tristate "AC Adapter"
depends on X86
next reply other threads:[~2007-08-27 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 15:04 Hugh Dickins [this message]
2007-08-27 17:39 ` Brown, Len
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=Pine.LNX.4.64.0708271602170.21853@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®