All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <54E184B6.90808@samsung.com>

diff --git a/a/1.txt b/N1/1.txt
index 133f525..df082cb 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -22,14 +22,14 @@ On 02/15/2015 08:41 PM, Javier Martinez Canillas wrote:
 >>
 > 
 > I faced the same 'Timeout sending command' error when trying to enable
-> support for the SDIO wifi chip attached to mmc@12210000 (mmc1) on an
+> support for the SDIO wifi chip attached to mmc at 12210000 (mmc1) on an
 > Exynos5420 Peach Pit Chromebook. On booting the kernel log shows:
 > 
 > mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
 > 
 > 0x202000 == SDMMC_CMD_UPD_CLK | SDMMC_CMD_PRV_DAT_WAIT so your patch
 > #2 dw_mci_setup_bus() avoids the mmc comand to time out. However, it
-> has a side effect since with your series the uSD that in mmc@12220000
+> has a side effect since with your series the uSD that in mmc at 12220000
 > (mmc2) fails to be detected and the kernel log shows:
 > 
 > [    5.466432] Waiting for root device /dev/mmcblk1p4...
diff --git a/a/content_digest b/N1/content_digest
index 2c6e026..1213a7c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,24 +1,10 @@
  "ref\01423828368-18456-1-git-send-email-addy.ke@rock-chips.com\0"
  "ref\01423894668-8886-1-git-send-email-addy.ke@rock-chips.com\0"
  "ref\0CABxcv==G_sKsvWHX6rJP7EUv8jE=01k-JeGGXgiwiCN53pxdmQ@mail.gmail.com\0"
- "From\0Jaehoon Chung <jh80.chung@samsung.com>\0"
- "Subject\0Re: [PATCH v4 0/3] about data busy\0"
+ "From\0jh80.chung@samsung.com (Jaehoon Chung)\0"
+ "Subject\0[PATCH v4 0/3] about data busy\0"
  "Date\0Mon, 16 Feb 2015 14:48:38 +0900\0"
- "To\0Javier Martinez Canillas <javier@dowhile0.org>"
- " Addy Ke <addy.ke@rock-chips.com>\0"
- "Cc\0Ulf Hansson <ulf.hansson@linaro.org>"
-  Olof Johansson <olof@lixom.net>
-  Alim Akhtar <alim.akhtar@gmail.com>
-  Andrzej Hajda <a.hajda@samsung.com>
-  Douglas Anderson <dianders@chromium.org>
- " Heiko St\303\274bner <heiko@sntech.de>"
-  cf@rock-chips.com
-  lintao@rock-chips.com
-  huangtao@rock-chips.com
-  Linux Kernel <linux-kernel@vger.kernel.org>
-  linux-mmc@vger.kernel.org <linux-mmc@vger.kernel.org>
-  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
- " linux-rockchip@lists.infradead.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
  "On 02/15/2015 08:41 PM, Javier Martinez Canillas wrote:\n"
@@ -45,14 +31,14 @@
  ">>\n"
  "> \n"
  "> I faced the same 'Timeout sending command' error when trying to enable\n"
- "> support for the SDIO wifi chip attached to mmc@12210000 (mmc1) on an\n"
+ "> support for the SDIO wifi chip attached to mmc at 12210000 (mmc1) on an\n"
  "> Exynos5420 Peach Pit Chromebook. On booting the kernel log shows:\n"
  "> \n"
  "> mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)\n"
  "> \n"
  "> 0x202000 == SDMMC_CMD_UPD_CLK | SDMMC_CMD_PRV_DAT_WAIT so your patch\n"
  "> #2 dw_mci_setup_bus() avoids the mmc comand to time out. However, it\n"
- "> has a side effect since with your series the uSD that in mmc@12220000\n"
+ "> has a side effect since with your series the uSD that in mmc at 12220000\n"
  "> (mmc2) fails to be detected and the kernel log shows:\n"
  "> \n"
  "> [    5.466432] Waiting for root device /dev/mmcblk1p4...\n"
@@ -120,4 +106,4 @@
  "> [1]: http://paste.debian.net/plain/148794\n"
  >
 
-6d89893bd7b7e6b93af51e9a30258b5a1351daae6955c6b979b468508a73f936
+11251abe4029ec172c2bfc8f962fe4bdb4b144fa08b34091b9d8de52669efe29

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.