>> s/extcntl/xen/ to make it clear why this code exists -- >> or is there an expected "external control" other than Xen? >> > >I dislike making Xen-specific changes. Ideally we can find a way to fit >these changes into some other abstraction which already exists, or if >added would be useful to more than one user. > > J The "external logic" is the way we trying to make it a generic abstraction, but right now I cannot told who would be the external entity except xen. Maybe in the future if other software want to leverage linux acpica, they would also use it. If people has other idea on the abstraction, I would be happy to hear that. BTW, Len, do you think the hook this patch adds to the acpi subsystem is OK, regardless its name being "xen" or "extcntl"? Best Regards Ke -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
