Yes, they were only there so a child device could set its
>> Unless I'm missing something, you've just broken the hierarchical
>> relationship that exists between the local APIC device and its
>> client devices (NMI watchdog, oprofile [which you didn't convert],
>> and perfctr [not merged into Linus' tree]).
>I'm aware of the necessary ancstral relationship, and I should have
>mentioned this in the first email. Proper ancestral order is maintained by
>virtue of the fact that child devices are registered after parent devices.
>Because of this, they are inserted into the list of system devices after
>their parents, so by walking the list in reverse order, you are guaranteed
>to suspend/shutdown the devices in the right order.
Ok. I'm used to having this spelled out explicitly, but walking the
list in insertion order / reverse insertion order should work too.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/