diff for duplicates of <AANLkTimz1YcJ=Me5ZmiwnHcOoa18X-NajX6PQy_g3UH8@mail.gmail.com>
diff --git a/a/1.txt b/N1/1.txt
index ff59c2f..d1b7947 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -10,17 +10,17 @@ On Mon, Jan 24, 2011 at 7:41 PM, Russell King - ARM Linux
>> >> >> On Sat, Jan 22, 2011 at 11:44:59PM -0500, Nicolas Pitre wrote:
>> >> >>> At least another person did post results:
>> >> >>>
->> >> >>> http://mid.gmane.org/20110117094602.GA2622@pulham.picochip.com
->> >> >>> http://mid.gmane.org/20110117110308.GC2622@pulham.picochip.com
+>> >> >>> http://mid.gmane.org/20110117094602.GA2622 at pulham.picochip.com
+>> >> >>> http://mid.gmane.org/20110117110308.GC2622 at pulham.picochip.com
>> >> >>
->> >> >> Slightly different patch - there were three revisions. I can't attach
+>> >> >> Slightly different patch - there were three revisions. ?I can't attach
>> >> >> a tested-by given to a different patch to this one.
>> >> >>
>> >> >>> > That means omap2plus_defconfig .38 mainline kernels
>> >> >>> > (including -stable) will remain potentially dangerous when run on
>> >> >>> > SMP capable hardware.
>> >> >>>
->> >> >>> I must admit that this series looks a bit large for stable IMHO. I
+>> >> >>> I must admit that this series looks a bit large for stable IMHO. ?I
>> >> >>> think that the fix for stable should limit itself only to prevent SMP
>> >> >>> from being selected if anything else than CPU_32v6K is selected.
>> >> >>
@@ -28,21 +28,21 @@ On Mon, Jan 24, 2011 at 7:41 PM, Russell King - ARM Linux
>> >> >>
>> >> >
>> >>
->> >> Boot tested the 14 patch series with CONFIG_SWP_EMULATE enabled, on
->> >> the following boards :
+>> >> ?Boot tested the 14 patch series ?with CONFIG_SWP_EMULATE enabled, on
+>> >> ?the following boards :
>> >>
>> >>
->> >> 1. Omap2420 SDP
+>> >> ? 1. Omap2420 SDP
>> >>
->> >> 2. Omap2430 SDP
+>> >> ? 2. Omap2430 SDP
>> >>
->> >> 3. Omap3430 SDP
+>> >> ? 3. Omap3430 SDP
>> >>
->> >> 4. Omap4 Blaze
+>> >> ? 4. Omap4 Blaze
>> >>
->> >> Tested-by: Sourav Poddar <sourav.poddar@ti.com>
+>> >> ? Tested-by: Sourav Poddar <sourav.poddar@ti.com>
>> >
->> > Thanks. It's also important to ascertain which filesystems were tested -
+>> > Thanks. ?It's also important to ascertain which filesystems were tested -
>> > could you let me know please?
>> >
>>
@@ -55,12 +55,8 @@ No.
>> Please let me know if you need some other
>> information.
>
-> I'm trying to find out what _type_ of filesystem. ext2, ext3, nfs, cramfs,
+> I'm trying to find out what _type_ of filesystem. ?ext2, ext3, nfs, cramfs,
> etc.
>
-nfs filesystem.
---
-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
\ No newline at end of file
+nfs filesystem.
\ No newline at end of file
diff --git a/a/content_digest b/N1/content_digest
index f229ef2..4fee6c8 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -29,21 +29,16 @@
"ref\00020110124141112.GM16202\@n2100.arm.linux.org.uk\0"
]
[
- "From\0Poddar, Sourav <sourav.poddar\@ti.com>\0"
+ "From\0sourav.poddar\@ti.com (Poddar, Sourav)\0"
]
[
- "Subject\0Re: [PATCH 02/14] ARM: bitops: switch set/clear/change bitops to use ldrex/strex\0"
+ "Subject\0[PATCH 02/14] ARM: bitops: switch set/clear/change bitops to use ldrex/strex\0"
]
[
"Date\0Mon, 24 Jan 2011 20:24:41 +0530\0"
]
[
- "To\0Russell King - ARM Linux <linux\@arm.linux.org.uk>\0"
-]
-[
- "Cc\0Nicolas Pitre <nico\@fluxnic.net>",
- " linux-arm-kernel\@lists.infradead.org",
- " linux-omap\@vger.kernel.org\0"
+ "To\0linux-arm-kernel\@lists.infradead.org\0"
]
[
"\0000:1\0"
@@ -64,17 +59,17 @@
">> >> >> On Sat, Jan 22, 2011 at 11:44:59PM -0500, Nicolas Pitre wrote:\n",
">> >> >>> At least another person did post results:\n",
">> >> >>>\n",
- ">> >> >>> http://mid.gmane.org/20110117094602.GA2622\@pulham.picochip.com\n",
- ">> >> >>> http://mid.gmane.org/20110117110308.GC2622\@pulham.picochip.com\n",
+ ">> >> >>> http://mid.gmane.org/20110117094602.GA2622 at pulham.picochip.com\n",
+ ">> >> >>> http://mid.gmane.org/20110117110308.GC2622 at pulham.picochip.com\n",
">> >> >>\n",
- ">> >> >> Slightly different patch - there were three revisions. \302\240I can't attach\n",
+ ">> >> >> Slightly different patch - there were three revisions. ?I can't attach\n",
">> >> >> a tested-by given to a different patch to this one.\n",
">> >> >>\n",
">> >> >>> > That means omap2plus_defconfig .38 mainline kernels\n",
">> >> >>> > (including -stable) will remain potentially dangerous when run on\n",
">> >> >>> > SMP capable hardware.\n",
">> >> >>>\n",
- ">> >> >>> I must admit that this series looks a bit large for stable IMHO. \302\240I\n",
+ ">> >> >>> I must admit that this series looks a bit large for stable IMHO. ?I\n",
">> >> >>> think that the fix for stable should limit itself only to prevent SMP\n",
">> >> >>> from being selected if anything else than CPU_32v6K is selected.\n",
">> >> >>\n",
@@ -82,21 +77,21 @@
">> >> >>\n",
">> >> >\n",
">> >>\n",
- ">> >> \302\240Boot tested the 14 patch series \302\240with CONFIG_SWP_EMULATE enabled, on\n",
- ">> >> \302\240the following boards :\n",
+ ">> >> ?Boot tested the 14 patch series ?with CONFIG_SWP_EMULATE enabled, on\n",
+ ">> >> ?the following boards :\n",
">> >>\n",
">> >>\n",
- ">> >> \302\240 1. Omap2420 SDP\n",
+ ">> >> ? 1. Omap2420 SDP\n",
">> >>\n",
- ">> >> \302\240 2. Omap2430 SDP\n",
+ ">> >> ? 2. Omap2430 SDP\n",
">> >>\n",
- ">> >> \302\240 3. Omap3430 SDP\n",
+ ">> >> ? 3. Omap3430 SDP\n",
">> >>\n",
- ">> >> \302\240 4. Omap4 Blaze\n",
+ ">> >> ? 4. Omap4 Blaze\n",
">> >>\n",
- ">> >> \302\240 Tested-by: Sourav Poddar <sourav.poddar\@ti.com>\n",
+ ">> >> ? Tested-by: Sourav Poddar <sourav.poddar\@ti.com>\n",
">> >\n",
- ">> > Thanks. \302\240It's also important to ascertain which filesystems were tested -\n",
+ ">> > Thanks. ?It's also important to ascertain which filesystems were tested -\n",
">> > could you let me know please?\n",
">> >\n",
">>\n",
@@ -109,15 +104,11 @@
">> Please let me know if you need some other\n",
">> information.\n",
">\n",
- "> I'm trying to find out what _type_ of filesystem. \302\240ext2, ext3, nfs, cramfs,\n",
+ "> I'm trying to find out what _type_ of filesystem. ?ext2, ext3, nfs, cramfs,\n",
"> etc.\n",
">\n",
"\n",
- "nfs filesystem.\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"
+ "nfs filesystem."
]
-c20d333a987c442fdc7927433973a882e6d4cebfcdf0a7af683a4ec4337c6106
+b68e87357f09662ee26a3cec51fab5bef359335044fd9c45c1ac0cb94a457015
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.