diff for duplicates of <87hb64ocyd.fsf@ti.com> diff --git a/a/1.txt b/N1/1.txt index 657d033..1a4baa8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -12,14 +12,14 @@ >> >> >> >> The main RFC is in the last patch, and everything leading up to it are >> >> misc. omap_device cleanups that make the last patch cleaner and ->> >> clearer. It's really the last patch that does the decoupling. +>> >> clearer. ?It's really the last patch that does the decoupling. >> >> >> >> This will be necessary if we're going to decouple the platform_device ->> >> creation from the omap_device/omap_hwmod creation etc. This patch +>> >> creation from the omap_device/omap_hwmod creation etc. ?This patch >> >> leaves them both done in omap_device_build(), but shows that they can >> >> be decoupled. >> > Can you pls mention baseline used for these patches? I tried applying on ->> > latest mainline, v3.0 and git://git.pwsan.com/linux-2.6 prcm-devel-3.1 +>> > latest mainline, v3.0 and ?git://git.pwsan.com/linux-2.6 prcm-devel-3.1 >> >> Oops, sorry. I forgot to mention it. >> @@ -56,7 +56,3 @@ I suspect your crash is because you're not also testing with the MMC runtime PM series that is merging for v3.1. 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 bf45a56..b74e0f1 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,16 +2,10 @@ "ref\020110727140457.GA8558@manju-desktop\0" "ref\0CALyTGODe8r9zr4fA+AX=-XhpLjNXKtfHzxFUWMNSehDawEDMBA@mail.gmail.com\0" "ref\020110728045057.GA31297@manju-desktop\0" - "From\0Kevin Hilman <khilman@ti.com>\0" - "Subject\0Re: [RFC/PATCH 0/7] decouple platform_device from omap_device\0" + "From\0khilman@ti.com (Kevin Hilman)\0" + "Subject\0[RFC/PATCH 0/7] decouple platform_device from omap_device\0" "Date\0Fri, 29 Jul 2011 16:59:38 -0700\0" - "To\0G" - " Manjunath Kondaiah <manjugk@ti.com>\0" - "Cc\0linux-omap@vger.kernel.org" - Paul Walmsley <paul@pwsan.com> - Grant Likely <grant.likely@secretlab.ca> - linux-arm-kernel@lists.infradead.org - " devicetree-discuss@lists.ozlabs.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "\"G, Manjunath Kondaiah\" <manjugk@ti.com> writes:\n" @@ -28,14 +22,14 @@ ">> >>\n" ">> >> The main RFC is in the last patch, and everything leading up to it are\n" ">> >> misc. omap_device cleanups that make the last patch cleaner and\n" - ">> >> clearer. \302\240It's really the last patch that does the decoupling.\n" + ">> >> clearer. ?It's really the last patch that does the decoupling.\n" ">> >>\n" ">> >> This will be necessary if we're going to decouple the platform_device\n" - ">> >> creation from the omap_device/omap_hwmod creation etc. \302\240This patch\n" + ">> >> creation from the omap_device/omap_hwmod creation etc. ?This patch\n" ">> >> leaves them both done in omap_device_build(), but shows that they can\n" ">> >> be decoupled.\n" ">> > Can you pls mention baseline used for these patches? I tried applying on\n" - ">> > latest mainline, v3.0 and \302\240git://git.pwsan.com/linux-2.6 prcm-devel-3.1\n" + ">> > latest mainline, v3.0 and ?git://git.pwsan.com/linux-2.6 prcm-devel-3.1\n" ">> \n" ">> Oops, sorry. I forgot to mention it.\n" ">> \n" @@ -71,10 +65,6 @@ "I suspect your crash is because you're not also testing with the MMC\n" "runtime PM series that is merging for v3.1.\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 -21ae55c331e690122b656542cb8b8364678b78c84305bdc0aa1895104eb814c1 +22772f47c5b5558ca311a500791c109becf9def8f138a2e4e11f992c765152f7
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.