diff for duplicates of <20180918145201.68adcb8d@bbrezillon> diff --git a/a/1.txt b/N1/1.txt index 741a363..43c21f4 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -29,7 +29,7 @@ defined even if not all of them are used. > > Does this restriction also exist for FSPI? > > Yes, I have seen that implementation and first tries with that same -> logic, using LUT_MODE instead of LUT_ADDR, but didn’t work for the +> logic, using LUT_MODE instead of LUT_ADDR, but didn?t work for the > FlexSPI controller. > > In this controller, we are having separate LUT_XX for RowAddress and @@ -67,7 +67,7 @@ which I'd like to avoid (as repeated many times before). > > My concern was for performance and that's why has done remap for the > 4MB buffer size so that if any subsequent Read request would come -> within the range then don’t have to perform remap and can just +> within the range then don?t have to perform remap and can just > directly do memcpy() > > I would re-visit again and see if getting any issue in doing direct diff --git a/a/content_digest b/N1/content_digest index 7809f4b..7897a7f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,21 +2,10 @@ "ref\01537177710-9379-2-git-send-email-yogeshnarayan.gaur@nxp.com\0" "ref\09a80752f-2db3-bf76-fbf4-e5efaa3974d7@exceet.de\0" "ref\0VI1PR04MB1038EDE4B2F5AFC5B0FDE8DF991D0@VI1PR04MB1038.eurprd04.prod.outlook.com\0" - "From\0Boris Brezillon <boris.brezillon@bootlin.com>\0" - "Subject\0Re: [PATCH v2 1/5] spi: spi-mem: Add driver for NXP FlexSPI controller\0" + "From\0boris.brezillon@bootlin.com (Boris Brezillon)\0" + "Subject\0[PATCH v2 1/5] spi: spi-mem: Add driver for NXP FlexSPI controller\0" "Date\0Tue, 18 Sep 2018 14:52:01 +0200\0" - "To\0Yogesh Narayan Gaur <yogeshnarayan.gaur@nxp.com>\0" - "Cc\0Frieder Schrempf <frieder.schrempf@exceet.de>" - linux-mtd@lists.infradead.org <linux-mtd@lists.infradead.org> - marek.vasut@gmail.com <marek.vasut@gmail.com> - linux-spi@vger.kernel.org <linux-spi@vger.kernel.org> - devicetree@vger.kernel.org <devicetree@vger.kernel.org> - robh@kernel.org <robh@kernel.org> - mark.rutland@arm.com <mark.rutland@arm.com> - shawnguo@kernel.org <shawnguo@kernel.org> - linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> - computersforpeace@gmail.com <computersforpeace@gmail.com> - " linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "Hi Yogesh,\n" @@ -50,7 +39,7 @@ "> > Does this restriction also exist for FSPI? \n" "> \n" "> Yes, I have seen that implementation and first tries with that same\n" - "> logic, using LUT_MODE instead of LUT_ADDR, but didn\342\200\231t work for the\n" + "> logic, using LUT_MODE instead of LUT_ADDR, but didn?t work for the\n" "> FlexSPI controller.\n" "> \n" "> In this controller, we are having separate LUT_XX for RowAddress and\n" @@ -88,7 +77,7 @@ "> \n" "> My concern was for performance and that's why has done remap for the\n" "> 4MB buffer size so that if any subsequent Read request would come\n" - "> within the range then don\342\200\231t have to perform remap and can just\n" + "> within the range then don?t have to perform remap and can just\n" "> directly do memcpy()\n" "> \n" "> I would re-visit again and see if getting any issue in doing direct\n" @@ -107,4 +96,4 @@ "\n" Boris -0e824233a1912d58192d8001b5222c1e0c1041487d8f7846210402ada1f7c3d8 +935f81cc3268bc41c91664198e060663fc86f92c6ec3881210bfe9a635abc813
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.