diff for duplicates of <000001d623a7$14bc6590$3e3530b0$@samsung.com>

diff --git a/a/1.txt b/N1/1.txt
index 26ea9ee..155ee05 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -2,39 +2,32 @@
 > -----Original Message-----
 > From: Will Deacon <will@kernel.org>
 > Sent: Wednesday, May 6, 2020 9:53 PM
-> To: �ֵ���/DONGHYEOK CHOE <d7271.choe@samsung.com>
-> Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;
-> hosung0.kim@samsung.com; changki.kim@samsung.com; hajun.sung@samsung.com;
-> gregkh@google.com; youngmin.nam@samsung.com
-> Subject: Re: Reqeust export symbol for API in arch/arm64/*
-> 
-> On Wed, May 06, 2020 at 09:46:45PM +0900,  ֵ   /DONGHYEOK CHOE wrote:
-> > I am software engineer in charge of BSP (Samsung SOC vendor).
-> >
-> > Recently, Google introduced GKI from Android R version.
-> > We cannot use mainline API without 'export symbol' by the GKI policy.
-> > But we want to make an arm64 specific vendor driver in {kernel source
-> > root}/drivers/soc/samsung/*.
-> >
-> > Could you support us to use the below APIs?
-> 
-> Sorry, but as a general rule of thumb the kernel doesn't EXPORT symbols
-> that are not used by in-tree modules. You'll need to submit your drivers
-> along with the patches doing the exports if they are to be considered for
-> inclusion.
-> 
-> Thanks,
-> 
-> Will
-
-Thank you for your quick response.
-I'll try.
-
+> To: �ֵ���/DONGHYEOK CHOE <d7271.choe@samsung.com>\r
+> Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;\r
+> hosung0.kim@samsung.com; changki.kim@samsung.com; hajun.sung@samsung.com;\r
+> gregkh@google.com; youngmin.nam@samsung.com\r
+> Subject: Re: Reqeust export symbol for API in arch/arm64/*\r
+> \r
+> On Wed, May 06, 2020 at 09:46:45PM +0900,  ֵ   /DONGHYEOK CHOE wrote:\r
+> > I am software engineer in charge of BSP (Samsung SOC vendor).\r
+> >\r
+> > Recently, Google introduced GKI from Android R version.\r
+> > We cannot use mainline API without 'export symbol' by the GKI policy.\r
+> > But we want to make an arm64 specific vendor driver in {kernel source\r
+> > root}/drivers/soc/samsung/*.\r
+> >\r
+> > Could you support us to use the below APIs?\r
+> \r
+> Sorry, but as a general rule of thumb the kernel doesn't EXPORT symbols\r
+> that are not used by in-tree modules. You'll need to submit your drivers\r
+> along with the patches doing the exports if they are to be considered for\r
+> inclusion.\r
+> \r
+> Thanks,\r
+> \r
+> Will\r
+\r
+Thank you for your quick response.\r
+I'll try.\r
+\r
 Thanks
-
-
-
-_______________________________________________
-linux-arm-kernel mailing list
-linux-arm-kernel@lists.infradead.org
-http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
diff --git a/a/content_digest b/N1/content_digest
index 7a44f46..98cbdf2 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,54 +5,47 @@
  "Subject\0RE: Reqeust export symbol for API in arch/arm64/*\0"
  "Date\0Wed, 6 May 2020 22:05:56 +0900\0"
  "To\0'Will Deacon' <will@kernel.org>\0"
- "Cc\0changki.kim@samsung.com"
-  linux-kernel@vger.kernel.org
-  youngmin.nam@samsung.com
-  hosung0.kim@samsung.com
-  hajun.sung@samsung.com
-  gregkh@google.com
- " linux-arm-kernel@lists.infradead.org\0"
+ "Cc\0<linux-arm-kernel@lists.infradead.org>"
+  <linux-kernel@vger.kernel.org>
+  <hosung0.kim@samsung.com>
+  <changki.kim@samsung.com>
+  <hajun.sung@samsung.com>
+  <gregkh@google.com>
+ " <youngmin.nam@samsung.com>\0"
  "\00:1\0"
  "b\0"
  "\n"
  "> -----Original Message-----\n"
  "> From: Will Deacon <will@kernel.org>\n"
  "> Sent: Wednesday, May 6, 2020 9:53 PM\n"
- "> To: \357\277\275\326\265\357\277\275\357\277\275\357\277\275/DONGHYEOK CHOE <d7271.choe@samsung.com>\n"
- "> Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;\n"
- "> hosung0.kim@samsung.com; changki.kim@samsung.com; hajun.sung@samsung.com;\n"
- "> gregkh@google.com; youngmin.nam@samsung.com\n"
- "> Subject: Re: Reqeust export symbol for API in arch/arm64/*\n"
- "> \n"
- "> On Wed, May 06, 2020 at 09:46:45PM +0900,  \326\265   /DONGHYEOK CHOE wrote:\n"
- "> > I am software engineer in charge of BSP (Samsung SOC vendor).\n"
- "> >\n"
- "> > Recently, Google introduced GKI from Android R version.\n"
- "> > We cannot use mainline API without 'export symbol' by the GKI policy.\n"
- "> > But we want to make an arm64 specific vendor driver in {kernel source\n"
- "> > root}/drivers/soc/samsung/*.\n"
- "> >\n"
- "> > Could you support us to use the below APIs?\n"
- "> \n"
- "> Sorry, but as a general rule of thumb the kernel doesn't EXPORT symbols\n"
- "> that are not used by in-tree modules. You'll need to submit your drivers\n"
- "> along with the patches doing the exports if they are to be considered for\n"
- "> inclusion.\n"
- "> \n"
- "> Thanks,\n"
- "> \n"
- "> Will\n"
- "\n"
- "Thank you for your quick response.\n"
- "I'll try.\n"
- "\n"
- "Thanks\n"
- "\n"
- "\n"
- "\n"
- "_______________________________________________\n"
- "linux-arm-kernel mailing list\n"
- "linux-arm-kernel@lists.infradead.org\n"
- http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
+ "> To: \357\277\275\326\265\357\277\275\357\277\275\357\277\275/DONGHYEOK CHOE <d7271.choe@samsung.com>\r\n"
+ "> Cc: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org;\r\n"
+ "> hosung0.kim@samsung.com; changki.kim@samsung.com; hajun.sung@samsung.com;\r\n"
+ "> gregkh@google.com; youngmin.nam@samsung.com\r\n"
+ "> Subject: Re: Reqeust export symbol for API in arch/arm64/*\r\n"
+ "> \r\n"
+ "> On Wed, May 06, 2020 at 09:46:45PM +0900,  \326\265   /DONGHYEOK CHOE wrote:\r\n"
+ "> > I am software engineer in charge of BSP (Samsung SOC vendor).\r\n"
+ "> >\r\n"
+ "> > Recently, Google introduced GKI from Android R version.\r\n"
+ "> > We cannot use mainline API without 'export symbol' by the GKI policy.\r\n"
+ "> > But we want to make an arm64 specific vendor driver in {kernel source\r\n"
+ "> > root}/drivers/soc/samsung/*.\r\n"
+ "> >\r\n"
+ "> > Could you support us to use the below APIs?\r\n"
+ "> \r\n"
+ "> Sorry, but as a general rule of thumb the kernel doesn't EXPORT symbols\r\n"
+ "> that are not used by in-tree modules. You'll need to submit your drivers\r\n"
+ "> along with the patches doing the exports if they are to be considered for\r\n"
+ "> inclusion.\r\n"
+ "> \r\n"
+ "> Thanks,\r\n"
+ "> \r\n"
+ "> Will\r\n"
+ "\r\n"
+ "Thank you for your quick response.\r\n"
+ "I'll try.\r\n"
+ "\r\n"
+ Thanks
 
-7b90da3d5647f1bf9d7bbc28fb953e4acf2d71d5ddb7fb451493de37c8486327
+ba16e111942e6b93b24876a329e8c71fd976a16530bbbe7ed6117a0c8c8cca5a
