diff for duplicates of <51D65CE8.4050004@ti.com> diff --git a/a/1.txt b/N1/1.txt index e9e2946..0fd108e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,7 +2,7 @@ On Thursday 04 July 2013 10:14 PM, Paul Walmsley wrote: > You mentioned that these patches were generated with some kind of awk/grep > scripting. Can you integrate that in an automated way into the > autogeneration flow? If the answer is yes, then keep the header. If the -> answer is no, then the header should be dropped. Benoît, maybe you have +> answer is no, then the header should be dropped. Beno?t, maybe you have > an opinion too? Ok, I'll try and integrate those scripts so all this can be done in an @@ -29,8 +29,3 @@ I don't mind these going in -rcX or 3.12, either way is fine. I will post these out as non-RFC after I do a clean integration into the autogen scripts, and then you can take a call on sending the pull for either -rcX or 3.12 - --- -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 c72b6ad..5980281 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -4,21 +4,17 @@ "ref\020130704115819.GJ5523@atomide.com\0" "ref\051D56743.9080800@ti.com\0" "ref\0alpine.DEB.2.02.1307041627540.6258@utopia.booyaka.com\0" - "From\0Rajendra Nayak <rnayak@ti.com>\0" - "Subject\0Re: [RFC 0/4] Cleanup PRM and CM regbit headers\0" + "From\0rnayak@ti.com (Rajendra Nayak)\0" + "Subject\0[RFC 0/4] Cleanup PRM and CM regbit headers\0" "Date\0Fri, 5 Jul 2013 11:13:04 +0530\0" - "To\0Paul Walmsley <paul@pwsan.com>\0" - "Cc\0benoit.cousson@gmail.com <benoit.cousson@gmail.com>" - Tony Lindgren <tony@atomide.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" "On Thursday 04 July 2013 10:14 PM, Paul Walmsley wrote:\n" "> You mentioned that these patches were generated with some kind of awk/grep \n" "> scripting. Can you integrate that in an automated way into the \n" "> autogeneration flow? If the answer is yes, then keep the header. If the \n" - "> answer is no, then the header should be dropped. Beno\303\256t, maybe you have \n" + "> answer is no, then the header should be dropped. Beno?t, maybe you have \n" "> an opinion too?\n" "\n" "Ok, I'll try and integrate those scripts so all this can be done in an\n" @@ -44,11 +40,6 @@ ":) I thought so too that you should be the one sending the pull.\n" "I will post these out as non-RFC after I do a clean integration into\n" "the autogen scripts, and then you can take a call on sending the pull for\n" - "either -rcX or 3.12\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 + either -rcX or 3.12 -1299c5ddc3bebc5fdcf2e81d13f92add7734d84260fe294064bcdeda9523f733 +c703cb7438207443a1477c3abec4c2589c1ae4c9a57cd70631a2ebf2cd8316e3
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.