diff for duplicates of <52284F32.2020302@freescale.com> diff --git a/a/1.txt b/N1/1.txt index bb9389d..40beb3d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -于 2013年09月05日 17:11, Gupta, Pekon 写道: +? 2013?09?05? 17:11, Gupta, Pekon ??: > No, SPI generic framework (struct spi_transfer, spi_message,...) > should be kept independent of any MTD flash specific data handlers. > <wangyuhang2014@gmail.com> added two new fields (tx_nbits, rx_nbits) @@ -28,7 +28,7 @@ ok. i think i do not need to change the spi code now. > demo board, so you can live with QUAD mode. > But when customer will have custom boards with different QSPI devices > then you would end-up supporting all sorts of configurations:-) -> And in production scenarios, it’s the price economics which mostly dominates +> And in production scenarios, it?s the price economics which mostly dominates > which part to choose and how to connect it on board. > Like as I remember some freescale boards have WINBOND QSPI flash > which uses different opcodes and semantics, so you might need to support diff --git a/a/content_digest b/N1/content_digest index 7092bdb..dbb37cf 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -11,30 +11,13 @@ "ref\020980858CB6D3A4BAE95CA194937D5E73EA0C885@DBDE04.ent.ti.com\0" "ref\05228369A.9000904@freescale.com\0" "ref\020980858CB6D3A4BAE95CA194937D5E73EA0C907@DBDE04.ent.ti.com\0" - "From\0Huang Shijie <b32955@freescale.com>\0" - "Subject\0Re: [PATCH v3 0/8] Add the Quadspi driver for vf610-twr\0" + "From\0b32955@freescale.com (Huang Shijie)\0" + "Subject\0[PATCH v3 0/8] Add the Quadspi driver for vf610-twr\0" "Date\0Thu, 5 Sep 2013 17:30:26 +0800\0" - "To\0Gupta" - " Pekon <pekon@ti.com>\0" - "Cc\0devicetree@vger.kernel.org <devicetree@vger.kernel.org>" - computersforpeace@gmail.com <computersforpeace@gmail.com> - b44548@freescale.com <b44548@freescale.com> - dedekind1@gmail.com <dedekind1@gmail.com> - dwmw2@infradead.org <dwmw2@infradead.org> - linux-doc@vger.kernel.org <linux-doc@vger.kernel.org> - b18965@freescale.com <b18965@freescale.com> - linux-spi@vger.kernel.org <linux-spi@vger.kernel.org> - thomas.langer@lantiq.com <thomas.langer@lantiq.com> - broonie@kernel.org <broonie@kernel.org> - linux-mtd@lists.infradead.org <linux-mtd@lists.infradead.org> - kernel@pengutronix.de <kernel@pengutronix.de> - lznuaa@gmail.com <lznuaa@gmail.com> - shawn.guo@linaro.org <shawn.guo@linaro.org> - Huang Shijie <shijie8@gmail.com> - " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" - "\344\272\216 2013\345\271\26409\346\234\21005\346\227\245 17:11, Gupta, Pekon \345\206\231\351\201\223:\n" + "? 2013?09?05? 17:11, Gupta, Pekon ??:\n" "> No, SPI generic framework (struct spi_transfer, spi_message,...)\n" "> should be kept independent of any MTD flash specific data handlers.\n" "> <wangyuhang2014@gmail.com> added two new fields (tx_nbits, rx_nbits)\n" @@ -64,7 +47,7 @@ "> demo board, so you can live with QUAD mode.\n" "> But when customer will have custom boards with different QSPI devices\n" "> then you would end-up supporting all sorts of configurations:-)\n" - "> And in production scenarios, it\342\200\231s the price economics which mostly dominates\n" + "> And in production scenarios, it?s the price economics which mostly dominates\n" "> which part to choose and how to connect it on board.\n" "> Like as I remember some freescale boards have WINBOND QSPI flash\n" "> which uses different opcodes and semantics, so you might need to support\n" @@ -87,4 +70,4 @@ "thanks\n" Huang Shijie -ab380cad2b1cc107d179986c768001e938b33e8a87f556eea67a151e47f628a5 +3510e77e83c18c1a71c2a0e32885f2898d5016981e04fca68fa29f2ca0daeb9a
diff --git a/a/content_digest b/N2/content_digest index 7092bdb..3364035 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -16,21 +16,21 @@ "Date\0Thu, 5 Sep 2013 17:30:26 +0800\0" "To\0Gupta" " Pekon <pekon@ti.com>\0" - "Cc\0devicetree@vger.kernel.org <devicetree@vger.kernel.org>" - computersforpeace@gmail.com <computersforpeace@gmail.com> + "Cc\0Huang Shijie <shijie8@gmail.com>" + thomas.langer@lantiq.com <thomas.langer@lantiq.com> + devicetree@vger.kernel.org <devicetree@vger.kernel.org> + shawn.guo@linaro.org <shawn.guo@linaro.org> b44548@freescale.com <b44548@freescale.com> dedekind1@gmail.com <dedekind1@gmail.com> - dwmw2@infradead.org <dwmw2@infradead.org> linux-doc@vger.kernel.org <linux-doc@vger.kernel.org> b18965@freescale.com <b18965@freescale.com> linux-spi@vger.kernel.org <linux-spi@vger.kernel.org> - thomas.langer@lantiq.com <thomas.langer@lantiq.com> broonie@kernel.org <broonie@kernel.org> linux-mtd@lists.infradead.org <linux-mtd@lists.infradead.org> kernel@pengutronix.de <kernel@pengutronix.de> lznuaa@gmail.com <lznuaa@gmail.com> - shawn.guo@linaro.org <shawn.guo@linaro.org> - Huang Shijie <shijie8@gmail.com> + computersforpeace@gmail.com <computersforpeace@gmail.com> + dwmw2@infradead.org <dwmw2@infradead.org> " linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>\0" "\00:1\0" "b\0" @@ -87,4 +87,4 @@ "thanks\n" Huang Shijie -ab380cad2b1cc107d179986c768001e938b33e8a87f556eea67a151e47f628a5 +5b2ea14b1876b9bebfb83e720f2eaa99db3a25ea82f954b56abf29035aa7380d
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.