diff for duplicates of <116291517513264@web58o.yandex.ru>

diff --git a/a/1.txt b/N1/1.txt
index 7f715c9..137d369 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -2,48 +2,48 @@
 
 01.02.2018, 21:03, "Greg KH" <greg@kroah.com>:
 > On Thu, Feb 01, 2018 at 06:33:30PM +0100, Ozan Alpay wrote:
->> ?Dear Rodrigo Vivi, Ville Syrj?l?,
+>>  Dear Rodrigo Vivi, Ville Syrjälä,
 >>
->> ?My name is Ozan Alpay, and I am a student mentored by Lukas Bulwahn. We
+>>  My name is Ozan Alpay, and I am a student mentored by Lukas Bulwahn. We
 
 Hi Ozan,
 
 why did you send e-mail to kernel development e-mail list?
 
->> ?intend to use static analysis tools on the kernel source to identify,
->> ?analyze and report issues. As a very first step, we are looking into
->> ?clang compiler warnings and will then move to more sophisticated tools.
+>>  intend to use static analysis tools on the kernel source to identify,
+>>  analyze and report issues. As a very first step, we are looking into
+>>  clang compiler warnings and will then move to more sophisticated tools.
 >>
->> ?When compiling Linux 4.15 with clang, we have discovered that your commit
->> ?2952cd6fb4cc ("drm/i915: Let's use more enum intel_dpll_id pll_id.")
->> ?introduced the following warning:
+>>  When compiling Linux 4.15 with clang, we have discovered that your commit
+>>  2952cd6fb4cc ("drm/i915: Let's use more enum intel_dpll_id pll_id.")
+>>  introduced the following warning:
 >>
->> ?drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion from enumeration type 'enum port' to different enumeration type 'enum intel_dpll_id' [-Wenum-conversion]
->> ?????????enum intel_dpll_id pll_id = port;
+>>  drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion from enumeration type 'enum port' to different enumeration type 'enum intel_dpll_id' [-Wenum-conversion]
+>>          enum intel_dpll_id pll_id = port;
 >>
->> ?To reproduce it, you can compile Linux 4.15 with clang with this command:
+>>  To reproduce it, you can compile Linux 4.15 with clang with this command:
 >>
->> ?make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0
+>>  make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0
 >>
->> ?If you don't have clang installed in your system, you can use this simple
->> ?docker setup to compile the kernel with clang:
+>>  If you don't have clang installed in your system, you can use this simple
+>>  docker setup to compile the kernel with clang:
 >>
->> ?wget https://raw.githubusercontent.com/bulwahn/linux-kernel-analysis/master/docker/kernel-clang/Dockerfile && \
->> ?docker build -t kernel-clang . && \
->> ?docker run -v <your kernel source directory>:/linux/ kernel-clang /bin/sh -c "cd linux && make CC=clang-5.0 clean && make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0"
+>>  wget https://raw.githubusercontent.com/bulwahn/linux-kernel-analysis/master/docker/kernel-clang/Dockerfile && \
+>>  docker build -t kernel-clang . && \
+>>  docker run -v <your kernel source directory>:/linux/ kernel-clang /bin/sh -c "cd linux && make CC=clang-5.0 clean && make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0"
 >>
->> ?While we were doing our analysis on 4.15, we noticed that you already
->> ?resolved this warning on linux-next with your work in commit bb911536f07e
->> ?("drm/i915: Eliminate pll->state usage from bxt_calc_pll_link()"). So,
->> ?since it is resolved on linux-next and we expect that this commit will be
->> ?merged in the merge window for 4.16, there is probably nothing further to
->> ?do.
+>>  While we were doing our analysis on 4.15, we noticed that you already
+>>  resolved this warning on linux-next with your work in commit bb911536f07e
+>>  ("drm/i915: Eliminate pll->state usage from bxt_calc_pll_link()"). So,
+>>  since it is resolved on linux-next and we expect that this commit will be
+>>  merged in the merge window for 4.16, there is probably nothing further to
+>>  do.
 >>
->> ?Linux 4.15 is shipped with this clang warning, but we don't see the
->> ?crucial need to provide a backport commit to the stable branch for 4.15.
->> ?We just wanted to inform you about our analysis of this clang warning.
->> ?Ultimately the final call if you would like to address this clang warning
->> ?in 4.15 is yours.
+>>  Linux 4.15 is shipped with this clang warning, but we don't see the
+>>  crucial need to provide a backport commit to the stable branch for 4.15.
+>>  We just wanted to inform you about our analysis of this clang warning.
+>>  Ultimately the final call if you would like to address this clang warning
+>>  in 4.15 is yours.
 >
 > Note, I have not taken "clang warning fixes" for stable kernel updates
 > in the past, and I doubt I will in the future, unless the tree "builds
@@ -62,3 +62,8 @@ why did you send e-mail to kernel development e-mail list?
 > greg k-h
 
 Ozgur
+
+_______________________________________________
+Kernelnewbies mailing list
+Kernelnewbies@kernelnewbies.org
+https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
diff --git a/a/content_digest b/N1/content_digest
index 548ae8d..9a43cd2 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,57 +1,70 @@
  "ref\0alpine.DEB.2.20.1802011823340.4316@alpaca\0"
  "ref\020180201180240.GA28042@kroah.com\0"
- "From\0o@zgur.org (Ozgur)\0"
- "Subject\0clang warning: implicit conversion in intel_ddi.c:1481\0"
+ "From\0Ozgur <o@zgur.org>\0"
+ "Subject\0Re: clang warning: implicit conversion in intel_ddi.c:1481\0"
  "Date\0Thu, 01 Feb 2018 22:27:44 +0300\0"
- "To\0kernelnewbies@lists.kernelnewbies.org\0"
+ "To\0Greg KH <greg@kroah.com>"
+ " Ozan Alpay <ozyalpy@gmail.com>\0"
+ "Cc\0sil2review@lists.osadl.org <sil2review@lists.osadl.org>"
+  kernelnewbies@kernelnewbies.org <kernelnewbies@kernelnewbies.org>
+  David Airlie <airlied@linux.ie>
+  intel-gfx@lists.freedesktop.org <intel-gfx@lists.freedesktop.org>
+  Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
+  llvmlinux@lists.linuxfoundation.org <llvmlinux@lists.linuxfoundation.org>
+  linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>
+  dri-devel@lists.freedesktop.org <dri-devel@lists.freedesktop.org>
+  Jani Nikula <jani.nikula@linux.intel.com>
+  Rodrigo Vivi <rodrigo.vivi@intel.com>
+  lukas.bulwahn@gmail.com <lukas.bulwahn@gmail.com>
+ " Ville Syrj\303\244l\303\244 <ville.syrjala@linux.intel.com>\0"
  "\00:1\0"
  "b\0"
  "\n"
  "\n"
  "01.02.2018, 21:03, \"Greg KH\" <greg@kroah.com>:\n"
  "> On Thu, Feb 01, 2018 at 06:33:30PM +0100, Ozan Alpay wrote:\n"
- ">> ?Dear Rodrigo Vivi, Ville Syrj?l?,\n"
+ ">> \302\240Dear Rodrigo Vivi, Ville Syrj\303\244l\303\244,\n"
  ">>\n"
- ">> ?My name is Ozan Alpay, and I am a student mentored by Lukas Bulwahn. We\n"
+ ">> \302\240My name is Ozan Alpay, and I am a student mentored by Lukas Bulwahn. We\n"
  "\n"
  "Hi Ozan,\n"
  "\n"
  "why did you send e-mail to kernel development e-mail list?\n"
  "\n"
- ">> ?intend to use static analysis tools on the kernel source to identify,\n"
- ">> ?analyze and report issues. As a very first step, we are looking into\n"
- ">> ?clang compiler warnings and will then move to more sophisticated tools.\n"
+ ">> \302\240intend to use static analysis tools on the kernel source to identify,\n"
+ ">> \302\240analyze and report issues. As a very first step, we are looking into\n"
+ ">> \302\240clang compiler warnings and will then move to more sophisticated tools.\n"
  ">>\n"
- ">> ?When compiling Linux 4.15 with clang, we have discovered that your commit\n"
- ">> ?2952cd6fb4cc (\"drm/i915: Let's use more enum intel_dpll_id pll_id.\")\n"
- ">> ?introduced the following warning:\n"
+ ">> \302\240When compiling Linux 4.15 with clang, we have discovered that your commit\n"
+ ">> \302\2402952cd6fb4cc (\"drm/i915: Let's use more enum intel_dpll_id pll_id.\")\n"
+ ">> \302\240introduced the following warning:\n"
  ">>\n"
- ">> ?drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion from enumeration type 'enum port' to different enumeration type 'enum intel_dpll_id' [-Wenum-conversion]\n"
- ">> ?????????enum intel_dpll_id pll_id = port;\n"
+ ">> \302\240drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion from enumeration type 'enum port' to different enumeration type 'enum intel_dpll_id' [-Wenum-conversion]\n"
+ ">> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240enum intel_dpll_id pll_id = port;\n"
  ">>\n"
- ">> ?To reproduce it, you can compile Linux 4.15 with clang with this command:\n"
+ ">> \302\240To reproduce it, you can compile Linux 4.15 with clang with this command:\n"
  ">>\n"
- ">> ?make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0\n"
+ ">> \302\240make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0\n"
  ">>\n"
- ">> ?If you don't have clang installed in your system, you can use this simple\n"
- ">> ?docker setup to compile the kernel with clang:\n"
+ ">> \302\240If you don't have clang installed in your system, you can use this simple\n"
+ ">> \302\240docker setup to compile the kernel with clang:\n"
  ">>\n"
- ">> ?wget https://raw.githubusercontent.com/bulwahn/linux-kernel-analysis/master/docker/kernel-clang/Dockerfile && \\\n"
- ">> ?docker build -t kernel-clang . && \\\n"
- ">> ?docker run -v <your kernel source directory>:/linux/ kernel-clang /bin/sh -c \"cd linux && make CC=clang-5.0 clean && make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0\"\n"
+ ">> \302\240wget https://raw.githubusercontent.com/bulwahn/linux-kernel-analysis/master/docker/kernel-clang/Dockerfile && \\\n"
+ ">> \302\240docker build -t kernel-clang . && \\\n"
+ ">> \302\240docker run -v <your kernel source directory>:/linux/ kernel-clang /bin/sh -c \"cd linux && make CC=clang-5.0 clean && make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0\"\n"
  ">>\n"
- ">> ?While we were doing our analysis on 4.15, we noticed that you already\n"
- ">> ?resolved this warning on linux-next with your work in commit bb911536f07e\n"
- ">> ?(\"drm/i915: Eliminate pll->state usage from bxt_calc_pll_link()\"). So,\n"
- ">> ?since it is resolved on linux-next and we expect that this commit will be\n"
- ">> ?merged in the merge window for 4.16, there is probably nothing further to\n"
- ">> ?do.\n"
+ ">> \302\240While we were doing our analysis on 4.15, we noticed that you already\n"
+ ">> \302\240resolved this warning on linux-next with your work in commit bb911536f07e\n"
+ ">> \302\240(\"drm/i915: Eliminate pll->state usage from bxt_calc_pll_link()\"). So,\n"
+ ">> \302\240since it is resolved on linux-next and we expect that this commit will be\n"
+ ">> \302\240merged in the merge window for 4.16, there is probably nothing further to\n"
+ ">> \302\240do.\n"
  ">>\n"
- ">> ?Linux 4.15 is shipped with this clang warning, but we don't see the\n"
- ">> ?crucial need to provide a backport commit to the stable branch for 4.15.\n"
- ">> ?We just wanted to inform you about our analysis of this clang warning.\n"
- ">> ?Ultimately the final call if you would like to address this clang warning\n"
- ">> ?in 4.15 is yours.\n"
+ ">> \302\240Linux 4.15 is shipped with this clang warning, but we don't see the\n"
+ ">> \302\240crucial need to provide a backport commit to the stable branch for 4.15.\n"
+ ">> \302\240We just wanted to inform you about our analysis of this clang warning.\n"
+ ">> \302\240Ultimately the final call if you would like to address this clang warning\n"
+ ">> \302\240in 4.15 is yours.\n"
  ">\n"
  "> Note, I have not taken \"clang warning fixes\" for stable kernel updates\n"
  "> in the past, and I doubt I will in the future, unless the tree \"builds\n"
@@ -69,6 +82,11 @@
  ">\n"
  "> greg k-h\n"
  "\n"
- Ozgur
+ "Ozgur\n"
+ "\n"
+ "_______________________________________________\n"
+ "Kernelnewbies mailing list\n"
+ "Kernelnewbies@kernelnewbies.org\n"
+ https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
 
-0ed5014f903491624e3f3d813806293d320f53656fa9bc79b516089cea516a07
+87d685c83dd061c61c0f0db51784fe250991d0318681a595fd9b6a9a8ca92cb7
