[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080111164904.3ca81602.akpm@linux-foundation.org>
Date: Fri, 11 Jan 2008 16:49:04 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: rjw@...k.pl, linux-pm@...ts.linux-foundation.org,
linux-acpi@...r.kernel.org, stern@...land.harvard.edu,
lenb@...nel.org, linux-kernel@...r.kernel.org, pavel@...e.cz,
mingo@...e.hu, gregkh@...e.de, tglx@...utronix.de, ak@...e.de
Subject: Re: [PATCH 0/4] PM: Do not destroy/create devices while suspended
(rev. 2)
On Fri, 11 Jan 2008 16:46:13 -0800
Andrew Morton <akpm@...ux-foundation.org> 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.
--
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