From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.28: How come some kernel options cannot be disabled for non-existent hardware?
Date: Tue, 30 Dec 2008 13:14:47 +0000 [thread overview]
Message-ID: <20081230131447.GA14942@srcf.ucam.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0812300641390.11356@p34.internal.lan>
On Tue, Dec 30, 2008 at 07:25:42AM -0500, Justin Piszcz wrote:
> It still shows up as enabled and it is in dmesg shown above. How come
> some kernel options are enabled and cannot (easily?) be disabled for
> hardware that does not exist in my machine?
It's enabled by the ATA_ACPI support so libata can handle ACPI-based
drive hotswaps. You can check these by looking at the help for an option
in make menuconfig. That'll tell you what's selecting an option.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-12-30 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 12:25 2.6.28: How come some kernel options cannot be disabled for non-existent hardware? Justin Piszcz
2008-12-30 13:14 ` Matthew Garrett [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-30 13:37 Nick Warne
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=20081230131447.GA14942@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.