| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <m2vck2lk4t.fsf@firstfloor.org> Date: Fri, 11 May 2012 10:09:38 -0700 From: Andi Kleen <andi@...stfloor.org> To: Toshi Kani <toshi.kani@...com> Cc: lenb@...nel.org, linux-acpi@...r.kernel.org, bhelgaas@...gle.com, shuahkhan@...il.com, liuj97@...il.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 0/7] ACPI: Add _OST support for ACPI hotplug Toshi Kani <toshi.kani@...com> writes: > This patchset supports ACPI OSPM Status Indication (_OST) method for > ACPI CPU/memory/container hotplug operations and sysfs eject. After > ACPI hotplug operation has completed, OSPM calls _OST to indicate the > result of the operation to the platform. If _OST is not present, this > patchset has no effect on the platform. > > This _OST support can be enabled or disabled with a new config option > CONFIG_ACPI_HOTPLUG_OST. This option is disabled by default. When > this option is disabled, this patchset has no effect on the platform. Does that control compiling in/out significant sized code? Controlling code behaviour by CONFIG option has been long deprecated. This is always better done as a runtime option. Just think what should a distribution who wants to use the same binary on all systems set. -Andi -- ak@...ux.intel.com -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists