Skip to contentSkip to conversation

i386: unexport acpi_strict

RFC PATCH In review Adrian Bunk 2 participants 2 messages Jan 20, 2005 ACPI

lore
Share & tools
lore
#0 lore raw

RFC PATCH 1/1 i386: unexport acpi_strict

I haven't found any possible modular usage of acpi_strict.

Is the patch below correct?

arch/i386/kernel/acpi/boot.c renamed from arch/i386/kernel/acpi/boot.c.old +0 -1
@@ -71,7 +71,6 @@
 int acpi_lapic;
 int acpi_ioapic;
 int acpi_strict;
-EXPORT_SYMBOL(acpi_strict);
 
 acpi_interrupt_flags acpi_sci_flags __initdata;
 int acpi_sci_override_gsi __initdata;

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl

#1 lore raw
Quoted 1 line · Adrian Bunk

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