On Fri, Jan 11, 2008 at 04:49:04PM -0800, Andrew Morton wrote: > On Fri, 11 Jan 2008 16:46:13 -0800 > Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > > The first patch in the series introduces such a mechanism. The remaining three > > > patches modify the MSR, x86-64 MCE and cpuid drivers in accordance with the > > > above approach. > > > > These patches are a preresuisite to > > gregkh-driver-pm-acquire-device-locks-prior-to-suspending.patch and its > > later fixed-up versions. > > > > So what I have now is > > > > revert-gregkh-driver-pm-acquire-device-locks-prior-to-suspending.patch > > pm-introduce-destroy_suspended_device.patch > > pm-do-not-destroy-create-devices-while-suspended-in-msrc-rev-2.patch > > pm-do-not-destroy-create-devices-while-suspended-in-mce_64c.patch > > pm-do-not-destroy-create-devices-while-suspended-in-cpuidc.patch > > pm-acquire-device-locks-on-suspend-rev-3.patch > > pm-acquire-device-locks-on-suspend-rev-3-checkpatch-fixes.patch > > pm-acquire-device-locks-on-suspend-rev-3-checkpatch-fixes-2.patch > > > > So what needs to happen in Greg's tree is > > > > a) drop the old gregkh-driver-pm-acquire-device-locks-prior-to-suspending.patch > > > > b) apply these four patches > > > > c) apply the new pm-acquire-device-locks-on-suspend-rev-3.patch (and its fixups) > > err, no. pm-introduce-destroy_suspended_device.patch demolishes > pm-acquire-device-locks-on-suspend-rev-3.patch > > Confused, giving up. I'm confused too, I have no idea what the proper order of things should be either. Anyone want to give me a hint? thanks, greg k-h - 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
