diff for duplicates of <87mx4p5niq.fsf@ti.com> diff --git a/a/1.txt b/N1/1.txt index a35b021..e70a94f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -12,7 +12,7 @@ >>>>>> >>> [...] >>>>>> - Rather than hooking into omap4_enter_lowpower(), should use ->>>>>> the cluster PM enter/exit notifier chain. +>>>>>> ?the cluster PM enter/exit notifier chain. >>>>>> >>>>> This is again specific to device OFF only and not related to CPU >>>>> cluster state as such. So I don't think notifiers should be used here. @@ -26,7 +26,7 @@ >>> >>> Like the overall idea, but one minor dumb concern might be sequencing >>> of notifiers ->>> - OFF entry and restore needs things to be executed in a specific sequence. +>>> ?- OFF entry and restore needs things to be executed in a specific sequence. >>> How do we plan to ensure the sequence is maintained in a notifier call >>> chain? one >>> possible option might be a "priority" based scheme? @@ -63,12 +63,3 @@ needs to be well described in the changlog. Thanks, Kevin - - - - - --- -To unsubscribe from this list: send the line "unsubscribe linux-omap" in -the body of a message to majordomo@vger.kernel.org -More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 89c0323..09fcd39 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,18 +6,10 @@ "ref\0CAOMWX4ctJcfGNxXK4hT+QH-m7zUfP1N3H56oVDVzPFmhVTFOMw@mail.gmail.com\0" "ref\087wr3t8s81.fsf@ti.com\0" "ref\0CAOMWX4ewVauzYW9pJq07=moLcgkBLyvx68o7T8975cGvshfK3Q@mail.gmail.com\0" - "From\0Kevin Hilman <khilman@ti.com>\0" - "Subject\0Re: [PATCHv2 04/19] ARM: OMAP4: PM: save/restore all DPLL settings in OFF mode\0" + "From\0khilman@ti.com (Kevin Hilman)\0" + "Subject\0[PATCHv2 04/19] ARM: OMAP4: PM: save/restore all DPLL settings in OFF mode\0" "Date\0Wed, 30 May 2012 15:09:49 -0700\0" - "To\0Menon" - " Nishanth <nm@ti.com>\0" - "Cc\0Shilimkar" - Santosh <santosh.shilimkar@ti.com> - paul@pwsan.com - Rajendra Nayak <rnayak@ti.com> - Tero Kristo <t-kristo@ti.com> - linux-omap@vger.kernel.org - " linux-arm-kernel@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "\"Menon, Nishanth\" <nm@ti.com> writes:\n" @@ -34,7 +26,7 @@ ">>>>>>\n" ">>> [...]\n" ">>>>>> - Rather than hooking into omap4_enter_lowpower(), should use\n" - ">>>>>> \302\240the cluster PM enter/exit notifier chain.\n" + ">>>>>> ?the cluster PM enter/exit notifier chain.\n" ">>>>>>\n" ">>>>> This is again specific to device OFF only and not related to CPU\n" ">>>>> cluster state as such. So I don't think notifiers should be used here.\n" @@ -48,7 +40,7 @@ ">>>\n" ">>> Like the overall idea, but one minor dumb concern might be sequencing\n" ">>> of notifiers\n" - ">>> \302\240- OFF entry and restore needs things to be executed in a specific sequence.\n" + ">>> ?- OFF entry and restore needs things to be executed in a specific sequence.\n" ">>> How do we plan to ensure the sequence is maintained in a notifier call\n" ">>> chain? one\n" ">>> possible option might be a \"priority\" based scheme?\n" @@ -84,15 +76,6 @@ "\n" "Thanks,\n" "\n" - "Kevin\n" - "\n" - "\n" - "\n" - "\n" - "\n" - "--\n" - "To unsubscribe from this list: send the line \"unsubscribe linux-omap\" in\n" - "the body of a message to majordomo@vger.kernel.org\n" - More majordomo info at http://vger.kernel.org/majordomo-info.html + Kevin -807c570ba240e627971cf6361564e381c34b477c16a33dadb81bf5d4a3692181 +f7f6b26812974684aa57e61b31d6a1790c4a7a0322810d55b71d11bea466bea4
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.