diff for duplicates of <87aa0qhm43.fsf@ti.com> diff --git a/a/1.txt b/N1/1.txt index f97b02b..d07c51f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -33,13 +33,13 @@ Jean Pihet <jean.pihet@newoldbits.com> writes: >>> these global flags all together. >>> >>> The way we manage the disabling of certain states (like off) is already ->>> clumsy for OMAP3, and it's getting worse with OMAP4. Basically, I think +>>> clumsy for OMAP3, and it's getting worse with OMAP4. ?Basically, I think >>> this feature needs to be supported by using constraints on functional ->>> power states. Having checks all over the place is getting unwieldy and +>>> power states. ? Having checks all over the place is getting unwieldy and >>> not attractive to maintain. >>> >>> The combination of constraints and functional power states should make ->>> this much more manageable. Until we have that, I'd prefer to keep +>>> this much more manageable. ? Until we have that, I'd prefer to keep >>> the debugfs enable/disable stuff as separate patches at the end of the >>> series used only for testing. >> @@ -47,7 +47,7 @@ Jean Pihet <jean.pihet@newoldbits.com> writes: >> >>> >>> > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com> ->>> > [t-kristo@ti.com: largely re-structured the code] +>>> > [t-kristo at ti.com: largely re-structured the code] >>> >>> then the sign-off above from Santosh probably doesn't apply anymore. >>> You should change that to a Cc and just mention tht this is based upon @@ -58,10 +58,10 @@ Jean Pihet <jean.pihet@newoldbits.com> writes: >> authors... will change this like so. >> >>> ->>> First, some general comments: +>>> First, ?some general comments: >>> >>> There is a lot going on in this patch, so it is hard to follow what all ->>> is related, and why. Just a quick glance suggests it needs to be broken +>>> is related, and why. ?Just a quick glance suggests it needs to be broken >>> up into at least a few parts: >> >> What is the merge plan for the func power state stuff? I don't want to @@ -82,7 +82,3 @@ For these reasons, I suggest basing this series on top of the functional power states series. 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 fbfb82b..cf5d260 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,15 +3,10 @@ "ref\087obpn92jy.fsf@ti.com\0" "ref\01337590125.2149.386.camel@sokoban\0" "ref\0CAORVsuWrDW-JAHWDNGMGshYxUUqZNURotreO7qW96=6+oKjyAQ@mail.gmail.com\0" - "From\0Kevin Hilman <khilman@ti.com>\0" - "Subject\0Re: [PATCHv2 03/19] ARM: OMAP4: PM: Add device-off support\0" + "From\0khilman@ti.com (Kevin Hilman)\0" + "Subject\0[PATCHv2 03/19] ARM: OMAP4: PM: Add device-off support\0" "Date\0Tue, 29 May 2012 11:34:52 -0700\0" - "To\0Jean Pihet <jean.pihet@newoldbits.com>\0" - "Cc\0t-kristo@ti.com" - Santosh Shilimkar <santosh.shilimkar@ti.com> - linux-omap@vger.kernel.org - paul@pwsan.com - " linux-arm-kernel@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Jean Pihet <jean.pihet@newoldbits.com> writes:\n" @@ -49,13 +44,13 @@ ">>> these global flags all together.\n" ">>>\n" ">>> The way we manage the disabling of certain states (like off) is already\n" - ">>> clumsy for OMAP3, and it's getting worse with OMAP4. \302\240Basically, I think\n" + ">>> clumsy for OMAP3, and it's getting worse with OMAP4. ?Basically, I think\n" ">>> this feature needs to be supported by using constraints on functional\n" - ">>> power states. \302\240 Having checks all over the place is getting unwieldy and\n" + ">>> power states. ? Having checks all over the place is getting unwieldy and\n" ">>> not attractive to maintain.\n" ">>>\n" ">>> The combination of constraints and functional power states should make\n" - ">>> this much more manageable. \302\240 Until we have that, I'd prefer to keep\n" + ">>> this much more manageable. ? Until we have that, I'd prefer to keep\n" ">>> the debugfs enable/disable stuff as separate patches at the end of the\n" ">>> series used only for testing.\n" ">>\n" @@ -63,7 +58,7 @@ ">>\n" ">>>\n" ">>> > Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>\n" - ">>> > [t-kristo@ti.com: largely re-structured the code]\n" + ">>> > [t-kristo at ti.com: largely re-structured the code]\n" ">>>\n" ">>> then the sign-off above from Santosh probably doesn't apply anymore.\n" ">>> You should change that to a Cc and just mention tht this is based upon\n" @@ -74,10 +69,10 @@ ">> authors... will change this like so.\n" ">>\n" ">>>\n" - ">>> First, \302\240some general comments:\n" + ">>> First, ?some general comments:\n" ">>>\n" ">>> There is a lot going on in this patch, so it is hard to follow what all\n" - ">>> is related, and why. \302\240Just a quick glance suggests it needs to be broken\n" + ">>> is related, and why. ?Just a quick glance suggests it needs to be broken\n" ">>> up into at least a few parts:\n" ">>\n" ">> What is the merge plan for the func power state stuff? I don't want to\n" @@ -97,10 +92,6 @@ "For these reasons, I suggest basing this series on top of the functional\n" "power states series.\n" "\n" - "Kevin\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 -e746034eb3b3bc24a8dd04ac477062b71c8f3f07880159317c2099ed2c09627f +9f07ec64744e1ee8777df8b9cf0dc038f6b8204988da4676c6ceccad8c7f6f99
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.