On Wed, 4 Oct 2006 23:56:02 -0400 Len Brown <len.brown@xxxxxxxxx> wrote: > I'm okay applying this patch it touches the linux-specific > drivers/acpi/* files only, no ACPICA files. Why? Would it help if it was split into two? How do mortals distinguish ACPICA files from Linux files? > But I don't know if Linus will want changes like this post -rc1. > It might be a pain to have in the tree all the way to 2.6.20 opens b/c > it is sure to cause merge conflicts Should be OK - the acpi tree is very slow-changing at present. Or did you have big changes planned? Or I can maintain it externally along with the 10-20 other acpi patches I seem to be regularly stuck with (hint ;) > -- and at the end of the day > the benefit of this patch is what? A few less characters in the source... > yes, cleanups are a pain, and we do a lot of them. And we merge just about all of them. But I think it's best in the long run; and we are in this for the long run. - 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
