From: Len Brown <len.brown@intel.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: ACPI Developers <acpi-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] i386: unexport acpi_strict
Date: 20 Jan 2005 13:39:11 -0500 [thread overview]
Message-ID: <1106246351.2395.11.camel@d845pe> (raw)
In-Reply-To: <20050120181527.GF3174@stusta.de>
On Thu, 2005-01-20 at 13:15, Adrian Bunk wrote:
> I haven't found any possible modular usage of acpi_strict.
I'd prefer to continue to export this flag if that isn't a burden.
The reason is that it is the only way we have to globally tell
the ACPI interpreter and all its (usually modularized) policy
drivers to allow or dis-allow support for platforms that openly
violate the ACPI spec. (By default the flag is clear and is
set explicity with "acpi_strict")
While the ACPI modules in the tree at the moment don't use
this flag, there are other out-of-tree
modules on the way, and they may need it.
-Len
prev parent reply other threads:[~2005-01-20 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 18:15 [RFC: 2.6 patch] i386: unexport acpi_strict Adrian Bunk
2005-01-20 18:39 ` Len Brown [this message]
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=1106246351.2395.11.camel@d845pe \
--to=len.brown@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=bunk@stusta.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox