All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <57C93F3E.4030802@samsung.com>

diff --git a/a/1.txt b/N1/1.txt
index 66f90df..6b4f48c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,4 +1,4 @@
-On 2016=EB=85=84 08=EC=9B=94 28=EC=9D=BC 01:33, Krzysztof Kozlowski wrote:
+On 2016년 08월 28일 01:33, Krzysztof Kozlowski wrote:
 > On Thu, Aug 25, 2016 at 03:57:18PM +0900, Chanwoo Choi wrote:
 >> This patch sets the clock rate for DREX (DRAM Express) block
 >> on exynos5422-odroidxu3 board. In the exynos5422 TRM,
@@ -7,11 +7,11 @@ On 2016=EB=85=84 08=EC=9B=94 28=EC=9D=BC 01:33, Krzysztof Kozlowski wrote:
 >>
 > 
 >>From the commit message I don't get two things:
-> 1. Why setting this on XU3-family of boards, not all 542x/5800=3F
+> 1. Why setting this on XU3-family of boards, not all 542x/5800?
 
 I have the only xu3 board. I cannot test it on other boards.
 
-> 2. Why this is needed=3F The commit msg lacks the answer to the "why".
+> 2. Why this is needed? The commit msg lacks the answer to the "why".
 
 In the exynos5422's TRM, CMU_CDREX generates the 800MHz DRAM clock
 as above commit message. But, I'm missing what there is different
@@ -27,8 +27,8 @@ clock rate for DRAM on below.
 >>           dout_sclk_cdrex              0            0   800000000          0 0
 >>
 > 
-> What is the purpose of this dump of clk_summary=3F Is it a state before or
-> after the change=3F After it is quite obvious that it should have
+> What is the purpose of this dump of clk_summary? Is it a state before or
+> after the change? After it is quite obvious that it should have
 > 800MHz...
 
 I'm missing the difference before applying this patch.
@@ -69,16 +69,16 @@ Chanwoo Choi
 >> --- a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
 >> +++ b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
 >> @@ -229,6 +229,11 @@
->>  	status =3D "okay";
+>>  	status = "okay";
 >>  };
 >>  
 >> +&clock {
->> +	assigned-clocks =3D <&clock CLK_DOUT_SCLK_CDREX>;
->> +	assigned-clock-rates =3D <800000000>;
+>> +	assigned-clocks = <&clock CLK_DOUT_SCLK_CDREX>;
+>> +	assigned-clock-rates = <800000000>;
 >> +};
 >> +
 >>  &clock_audss {
->>  	assigned-clocks =3D <&clock_audss EXYNOS_MOUT_AUDSS>,
+>>  	assigned-clocks = <&clock_audss EXYNOS_MOUT_AUDSS>,
 >>  			<&clock_audss EXYNOS_MOUT_I2S>,
 >> -- 
 >> 1.9.1
diff --git a/a/content_digest b/N1/content_digest
index df3c1d9..fa7be1c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -19,7 +19,7 @@
  " linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
- "On 2016=EB=85=84 08=EC=9B=94 28=EC=9D=BC 01:33, Krzysztof Kozlowski wrote:\n"
+ "On 2016\353\205\204 08\354\233\224 28\354\235\274 01:33, Krzysztof Kozlowski wrote:\n"
  "> On Thu, Aug 25, 2016 at 03:57:18PM +0900, Chanwoo Choi wrote:\n"
  ">> This patch sets the clock rate for DREX (DRAM Express) block\n"
  ">> on exynos5422-odroidxu3 board. In the exynos5422 TRM,\n"
@@ -28,11 +28,11 @@
  ">>\n"
  "> \n"
  ">>From the commit message I don't get two things:\n"
- "> 1. Why setting this on XU3-family of boards, not all 542x/5800=3F\n"
+ "> 1. Why setting this on XU3-family of boards, not all 542x/5800?\n"
  "\n"
  "I have the only xu3 board. I cannot test it on other boards.\n"
  "\n"
- "> 2. Why this is needed=3F The commit msg lacks the answer to the \"why\".\n"
+ "> 2. Why this is needed? The commit msg lacks the answer to the \"why\".\n"
  "\n"
  "In the exynos5422's TRM, CMU_CDREX generates the 800MHz DRAM clock\n"
  "as above commit message. But, I'm missing what there is different\n"
@@ -48,8 +48,8 @@
  ">>           dout_sclk_cdrex              0            0   800000000          0 0\n"
  ">>\n"
  "> \n"
- "> What is the purpose of this dump of clk_summary=3F Is it a state before or\n"
- "> after the change=3F After it is quite obvious that it should have\n"
+ "> What is the purpose of this dump of clk_summary? Is it a state before or\n"
+ "> after the change? After it is quite obvious that it should have\n"
  "> 800MHz...\n"
  "\n"
  "I'm missing the difference before applying this patch.\n"
@@ -90,16 +90,16 @@
  ">> --- a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi\n"
  ">> +++ b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi\n"
  ">> @@ -229,6 +229,11 @@\n"
- ">>  \tstatus =3D \"okay\";\n"
+ ">>  \tstatus = \"okay\";\n"
  ">>  };\n"
  ">>  \n"
  ">> +&clock {\n"
- ">> +\tassigned-clocks =3D <&clock CLK_DOUT_SCLK_CDREX>;\n"
- ">> +\tassigned-clock-rates =3D <800000000>;\n"
+ ">> +\tassigned-clocks = <&clock CLK_DOUT_SCLK_CDREX>;\n"
+ ">> +\tassigned-clock-rates = <800000000>;\n"
  ">> +};\n"
  ">> +\n"
  ">>  &clock_audss {\n"
- ">>  \tassigned-clocks =3D <&clock_audss EXYNOS_MOUT_AUDSS>,\n"
+ ">>  \tassigned-clocks = <&clock_audss EXYNOS_MOUT_AUDSS>,\n"
  ">>  \t\t\t<&clock_audss EXYNOS_MOUT_I2S>,\n"
  ">> -- \n"
  ">> 1.9.1\n"
@@ -117,4 +117,4 @@
  "> \n"
  >
 
-3a3bae0cbc677850246fc6f4f8032c13eefe52a0cf0a83cc04b616ee7c6bf0ce
+f70e16825dadc45ab2887aecad9415fcea0ec594dc1f6f7838e3dd6784b47ec0

diff --git a/a/1.txt b/N2/1.txt
index 66f90df..dde12a3 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,4 +1,4 @@
-On 2016=EB=85=84 08=EC=9B=94 28=EC=9D=BC 01:33, Krzysztof Kozlowski wrote:
+On 2016? 08? 28? 01:33, Krzysztof Kozlowski wrote:
 > On Thu, Aug 25, 2016 at 03:57:18PM +0900, Chanwoo Choi wrote:
 >> This patch sets the clock rate for DREX (DRAM Express) block
 >> on exynos5422-odroidxu3 board. In the exynos5422 TRM,
@@ -7,11 +7,11 @@ On 2016=EB=85=84 08=EC=9B=94 28=EC=9D=BC 01:33, Krzysztof Kozlowski wrote:
 >>
 > 
 >>From the commit message I don't get two things:
-> 1. Why setting this on XU3-family of boards, not all 542x/5800=3F
+> 1. Why setting this on XU3-family of boards, not all 542x/5800?
 
 I have the only xu3 board. I cannot test it on other boards.
 
-> 2. Why this is needed=3F The commit msg lacks the answer to the "why".
+> 2. Why this is needed? The commit msg lacks the answer to the "why".
 
 In the exynos5422's TRM, CMU_CDREX generates the 800MHz DRAM clock
 as above commit message. But, I'm missing what there is different
@@ -27,8 +27,8 @@ clock rate for DRAM on below.
 >>           dout_sclk_cdrex              0            0   800000000          0 0
 >>
 > 
-> What is the purpose of this dump of clk_summary=3F Is it a state before or
-> after the change=3F After it is quite obvious that it should have
+> What is the purpose of this dump of clk_summary? Is it a state before or
+> after the change? After it is quite obvious that it should have
 > 800MHz...
 
 I'm missing the difference before applying this patch.
@@ -69,16 +69,16 @@ Chanwoo Choi
 >> --- a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
 >> +++ b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi
 >> @@ -229,6 +229,11 @@
->>  	status =3D "okay";
+>>  	status = "okay";
 >>  };
 >>  
 >> +&clock {
->> +	assigned-clocks =3D <&clock CLK_DOUT_SCLK_CDREX>;
->> +	assigned-clock-rates =3D <800000000>;
+>> +	assigned-clocks = <&clock CLK_DOUT_SCLK_CDREX>;
+>> +	assigned-clock-rates = <800000000>;
 >> +};
 >> +
 >>  &clock_audss {
->>  	assigned-clocks =3D <&clock_audss EXYNOS_MOUT_AUDSS>,
+>>  	assigned-clocks = <&clock_audss EXYNOS_MOUT_AUDSS>,
 >>  			<&clock_audss EXYNOS_MOUT_I2S>,
 >> -- 
 >> 1.9.1
@@ -86,11 +86,11 @@ Chanwoo Choi
 >>
 >> _______________________________________________
 >> linux-arm-kernel mailing list
->> linux-arm-kernel@lists.infradead.org
+>> linux-arm-kernel at lists.infradead.org
 >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
 > --
 > To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
-> the body of a message to majordomo@vger.kernel.org
+> the body of a message to majordomo at vger.kernel.org
 > More majordomo info at  http://vger.kernel.org/majordomo-info.html
 > 
 > 
diff --git a/a/content_digest b/N2/content_digest
index df3c1d9..2427993 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -2,24 +2,13 @@
  "ref\01472108238-24309-4-git-send-email-cw00.choi@samsung.com\0"
  "ref\0CGME20160827163323epcas1p36e8aa80709136d2784f38f4531a5dab8@epcas1p3.samsung.com\0"
  "ref\020160827163310.GA8616@kozik-book\0"
- "From\0Chanwoo Choi <cw00.choi@samsung.com>\0"
- "Subject\0Re: [PATCH v2 3/3] ARM: dts: Set the clock rate for DREX block 800Mhz on exynos5422-odroidxu3\0"
+ "From\0cw00.choi@samsung.com (Chanwoo Choi)\0"
+ "Subject\0[PATCH v2 3/3] ARM: dts: Set the clock rate for DREX block 800Mhz on exynos5422-odroidxu3\0"
  "Date\0Fri, 02 Sep 2016 17:58:38 +0900\0"
- "To\0Krzysztof Kozlowski <krzk@kernel.org>\0"
- "Cc\0s.nawrocki@samsung.com"
-  tomasz.figa@gmail.com
-  k.kozlowski@samsung.com
-  linux-samsung-soc@vger.kernel.org
-  mturquette@baylibre.com
-  sboyd@codeaurora.org
-  linux-kernel@vger.kernel.org
-  kgene@kernel.org
-  chanwoo@kernel.org
-  linux-clk@vger.kernel.org
- " linux-arm-kernel@lists.infradead.org\0"
+ "To\0linux-arm-kernel@lists.infradead.org\0"
  "\00:1\0"
  "b\0"
- "On 2016=EB=85=84 08=EC=9B=94 28=EC=9D=BC 01:33, Krzysztof Kozlowski wrote:\n"
+ "On 2016? 08? 28? 01:33, Krzysztof Kozlowski wrote:\n"
  "> On Thu, Aug 25, 2016 at 03:57:18PM +0900, Chanwoo Choi wrote:\n"
  ">> This patch sets the clock rate for DREX (DRAM Express) block\n"
  ">> on exynos5422-odroidxu3 board. In the exynos5422 TRM,\n"
@@ -28,11 +17,11 @@
  ">>\n"
  "> \n"
  ">>From the commit message I don't get two things:\n"
- "> 1. Why setting this on XU3-family of boards, not all 542x/5800=3F\n"
+ "> 1. Why setting this on XU3-family of boards, not all 542x/5800?\n"
  "\n"
  "I have the only xu3 board. I cannot test it on other boards.\n"
  "\n"
- "> 2. Why this is needed=3F The commit msg lacks the answer to the \"why\".\n"
+ "> 2. Why this is needed? The commit msg lacks the answer to the \"why\".\n"
  "\n"
  "In the exynos5422's TRM, CMU_CDREX generates the 800MHz DRAM clock\n"
  "as above commit message. But, I'm missing what there is different\n"
@@ -48,8 +37,8 @@
  ">>           dout_sclk_cdrex              0            0   800000000          0 0\n"
  ">>\n"
  "> \n"
- "> What is the purpose of this dump of clk_summary=3F Is it a state before or\n"
- "> after the change=3F After it is quite obvious that it should have\n"
+ "> What is the purpose of this dump of clk_summary? Is it a state before or\n"
+ "> after the change? After it is quite obvious that it should have\n"
  "> 800MHz...\n"
  "\n"
  "I'm missing the difference before applying this patch.\n"
@@ -90,16 +79,16 @@
  ">> --- a/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi\n"
  ">> +++ b/arch/arm/boot/dts/exynos5422-odroidxu3-common.dtsi\n"
  ">> @@ -229,6 +229,11 @@\n"
- ">>  \tstatus =3D \"okay\";\n"
+ ">>  \tstatus = \"okay\";\n"
  ">>  };\n"
  ">>  \n"
  ">> +&clock {\n"
- ">> +\tassigned-clocks =3D <&clock CLK_DOUT_SCLK_CDREX>;\n"
- ">> +\tassigned-clock-rates =3D <800000000>;\n"
+ ">> +\tassigned-clocks = <&clock CLK_DOUT_SCLK_CDREX>;\n"
+ ">> +\tassigned-clock-rates = <800000000>;\n"
  ">> +};\n"
  ">> +\n"
  ">>  &clock_audss {\n"
- ">>  \tassigned-clocks =3D <&clock_audss EXYNOS_MOUT_AUDSS>,\n"
+ ">>  \tassigned-clocks = <&clock_audss EXYNOS_MOUT_AUDSS>,\n"
  ">>  \t\t\t<&clock_audss EXYNOS_MOUT_I2S>,\n"
  ">> -- \n"
  ">> 1.9.1\n"
@@ -107,14 +96,14 @@
  ">>\n"
  ">> _______________________________________________\n"
  ">> linux-arm-kernel mailing list\n"
- ">> linux-arm-kernel@lists.infradead.org\n"
+ ">> linux-arm-kernel at lists.infradead.org\n"
  ">> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel\n"
  "> --\n"
  "> To unsubscribe from this list: send the line \"unsubscribe linux-samsung-soc\" in\n"
- "> the body of a message to majordomo@vger.kernel.org\n"
+ "> the body of a message to majordomo at vger.kernel.org\n"
  "> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"
  "> \n"
  "> \n"
  >
 
-3a3bae0cbc677850246fc6f4f8032c13eefe52a0cf0a83cc04b616ee7c6bf0ce
+5a90339fcea17a55fce4d9ef32bca1490d99a2124dad842eb288d5871da76564

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.