diff for duplicates of <20100930221111.GO3117@atomide.com> diff --git a/a/1.txt b/N1/1.txt index 853af39..744a76f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,11 +1,11 @@ * Tony Lindgren <tony@atomide.com> [100930 12:07]: -> * Michał Mirosław <mirqus@gmail.com> [100930 11:57]: +> * Micha? Miros?aw <mirqus@gmail.com> [100930 11:57]: > > 2010/9/30 Tony Lindgren <tony@atomide.com>: > > > * Cory Maccarrone <darkstar6262@gmail.com> [100930 11:34]: > > >> > Looks like also board-sx1-mmc.c and board-h[23]-mmc.c have the > > >> > same spotty voltage range. > > >> > Cory, care to do a patch that fixes it for all of them? -> > >> Yeah, I can do that. I'll resubmit this patch too with the fixed up ranges. +> > >> Yeah, I can do that. ?I'll resubmit this patch too with the fixed up ranges. > > > Turns out I already did it :) Care to test/ack this one? > > > > [...] @@ -14,15 +14,15 @@ > > > --- a/arch/arm/mach-omap1/board-sx1-mmc.c > > > +++ b/arch/arm/mach-omap1/board-sx1-mmc.c > > > @@ -44,7 +44,8 @@ static struct omap_mmc_platform_data mmc1_data = { -> > > .nr_slots = 1, -> > > .slots[0] = { -> > > .set_power = mmc_set_power, -> > > - .ocr_mask = MMC_VDD_28_29 | MMC_VDD_30_31 | -> > > + .ocr_mask = MMC_VDD_28_29 | MMC_VDD_29_30 | -> > > + MMC_VDD_30_31 | MMC_VDD_31_32 | -> > > MMC_VDD_32_33 | MMC_VDD_33_34, -> > > .name = "mmcblk", -> > > }, +> > > ? ? ? ?.nr_slots ? ? ? ? ? ? ? ? ? ? ? = 1, +> > > ? ? ? ?.slots[0] ? ? ? = { +> > > ? ? ? ? ? ? ? ?.set_power ? ? ? ? ? ? ?= mmc_set_power, +> > > - ? ? ? ? ? ? ? .ocr_mask ? ? ? ? ? ? ? = MMC_VDD_28_29 | MMC_VDD_30_31 | +> > > + ? ? ? ? ? ? ? .ocr_mask ? ? ? ? ? ? ? = MMC_VDD_28_29 | MMC_VDD_29_30 | +> > > + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? MMC_VDD_30_31 | MMC_VDD_31_32 | +> > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?MMC_VDD_32_33 | MMC_VDD_33_34, +> > > ? ? ? ? ? ? ? ?.name ? ? ? ? ? ? ? ? ? = "mmcblk", +> > > ? ? ? ?}, > > [...] > > > > Al least this one seems wrong (haven't checked others) as the @@ -42,13 +42,13 @@ Tony From: Tony Lindgren <tony@atomide.com> Subject: [PATCH] omap: Fix spotty MMC voltages -As noted by Michał Mirosław <mirqus@gmail.com>, the voltages should +As noted by Micha? Miros?aw <mirqus@gmail.com>, the voltages should cover the supported voltage range, or support only one voltage. As all these boards are using a GPIO to enable the power, chances are that only 3.3V cards are supported on these boards. -Reported-by: Michał Mirosław <mirqus@gmail.com> +Reported-by: Micha? Miros?aw <mirqus@gmail.com> Signed-off-by: Tony Lindgren <tony@atomide.com> diff --git a/arch/arm/mach-omap1/board-h2-mmc.c b/arch/arm/mach-omap1/board-h2-mmc.c @@ -107,7 +107,3 @@ index 5b33ae8..e8ddd86 100644 .name = "mmcblk", }, }; --- -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 26cf233..b269b48 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,23 +8,20 @@ "ref\020100930184841.GL3117@atomide.com\0" "ref\0AANLkTimsk+vbi15xz5bxJyQrF0yXF3i7Dn=TajjV3tkU@mail.gmail.com\0" "ref\020100930191535.GM3117@atomide.com\0" - "From\0Tony Lindgren <tony@atomide.com>\0" - "Subject\0Re: [PATCH] [OMAP] HTCHERALD: MMC, I2C, HTCPLD, SPI, TSC2046\0" + "From\0tony@atomide.com (Tony Lindgren)\0" + "Subject\0[PATCH] [OMAP] HTCHERALD: MMC, I2C, HTCPLD, SPI, TSC2046\0" "Date\0Thu, 30 Sep 2010 15:11:11 -0700\0" - "To\0Micha\305\202 Miros\305\202aw <mirqus@gmail.com>\0" - "Cc\0Cory Maccarrone <darkstar6262@gmail.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" "* Tony Lindgren <tony@atomide.com> [100930 12:07]:\n" - "> * Micha\305\202 Miros\305\202aw <mirqus@gmail.com> [100930 11:57]:\n" + "> * Micha? Miros?aw <mirqus@gmail.com> [100930 11:57]:\n" "> > 2010/9/30 Tony Lindgren <tony@atomide.com>:\n" "> > > * Cory Maccarrone <darkstar6262@gmail.com> [100930 11:34]:\n" "> > >> > Looks like also board-sx1-mmc.c and board-h[23]-mmc.c have the\n" "> > >> > same spotty voltage range.\n" "> > >> > Cory, care to do a patch that fixes it for all of them?\n" - "> > >> Yeah, I can do that. \302\240I'll resubmit this patch too with the fixed up ranges.\n" + "> > >> Yeah, I can do that. ?I'll resubmit this patch too with the fixed up ranges.\n" "> > > Turns out I already did it :) Care to test/ack this one?\n" "> > \n" "> > [...]\n" @@ -33,15 +30,15 @@ "> > > --- a/arch/arm/mach-omap1/board-sx1-mmc.c\n" "> > > +++ b/arch/arm/mach-omap1/board-sx1-mmc.c\n" "> > > @@ -44,7 +44,8 @@ static struct omap_mmc_platform_data mmc1_data = {\n" - "> > > \302\240 \302\240 \302\240 \302\240.nr_slots \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 = 1,\n" - "> > > \302\240 \302\240 \302\240 \302\240.slots[0] \302\240 \302\240 \302\240 = {\n" - "> > > \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240.set_power \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240= mmc_set_power,\n" - "> > > - \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 .ocr_mask \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 = MMC_VDD_28_29 | MMC_VDD_30_31 |\n" - "> > > + \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 .ocr_mask \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 = MMC_VDD_28_29 | MMC_VDD_29_30 |\n" - "> > > + \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 MMC_VDD_30_31 | MMC_VDD_31_32 |\n" - "> > > \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240MMC_VDD_32_33 | MMC_VDD_33_34,\n" - "> > > \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240.name \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 \302\240 = \"mmcblk\",\n" - "> > > \302\240 \302\240 \302\240 \302\240},\n" + "> > > ? ? ? ?.nr_slots ? ? ? ? ? ? ? ? ? ? ? = 1,\n" + "> > > ? ? ? ?.slots[0] ? ? ? = {\n" + "> > > ? ? ? ? ? ? ? ?.set_power ? ? ? ? ? ? ?= mmc_set_power,\n" + "> > > - ? ? ? ? ? ? ? .ocr_mask ? ? ? ? ? ? ? = MMC_VDD_28_29 | MMC_VDD_30_31 |\n" + "> > > + ? ? ? ? ? ? ? .ocr_mask ? ? ? ? ? ? ? = MMC_VDD_28_29 | MMC_VDD_29_30 |\n" + "> > > + ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? MMC_VDD_30_31 | MMC_VDD_31_32 |\n" + "> > > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?MMC_VDD_32_33 | MMC_VDD_33_34,\n" + "> > > ? ? ? ? ? ? ? ?.name ? ? ? ? ? ? ? ? ? = \"mmcblk\",\n" + "> > > ? ? ? ?},\n" "> > [...]\n" "> > \n" "> > Al least this one seems wrong (haven't checked others) as the\n" @@ -61,13 +58,13 @@ "From: Tony Lindgren <tony@atomide.com>\n" "Subject: [PATCH] omap: Fix spotty MMC voltages\n" "\n" - "As noted by Micha\305\202 Miros\305\202aw <mirqus@gmail.com>, the voltages should\n" + "As noted by Micha? Miros?aw <mirqus@gmail.com>, the voltages should\n" "cover the supported voltage range, or support only one voltage.\n" "\n" "As all these boards are using a GPIO to enable the power, chances\n" "are that only 3.3V cards are supported on these boards.\n" "\n" - "Reported-by: Micha\305\202 Miros\305\202aw <mirqus@gmail.com>\n" + "Reported-by: Micha? Miros?aw <mirqus@gmail.com>\n" "Signed-off-by: Tony Lindgren <tony@atomide.com>\n" "\n" "diff --git a/arch/arm/mach-omap1/board-h2-mmc.c b/arch/arm/mach-omap1/board-h2-mmc.c\n" @@ -125,10 +122,6 @@ "+\t\t.ocr_mask = MMC_VDD_32_33 | MMC_VDD_33_34,\n" " \t\t.name = \"mmcblk\",\n" " \t},\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 + }; -227b4da261c3b57a1392d401db2c28840c02eb7d4abc295a4e850bb4305efcb5 +ec1aa098a4556db13b235bc949674f5ddf59cdca00d6c5a24a9031241e9d8740
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.