diff for duplicates of <HE1PR0802MB24127EC935B9AF6F82AB3B6EEE7E0@HE1PR0802MB2412.eurprd08.prod.outlook.com>
diff --git a/a/1.txt b/N2/1.txt
index b38fa3e..3b58452 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -1,11 +1,11 @@
Hi Suzuki,
-> > Why not use “unit”?
+> > Why not use ?unit??
> >
> > I believe we had this discussion years ago about numbering serial ports
-> > and sdhci (i.e. how do you know it’s UART0 or UART1 from just the address?
-> > Some SoC’s don’t address sequentially *or* in a forward direction) - I
-> > believe it’s not exactly codified in ePAPR, not am I sure where it may be
+> > and sdhci (i.e. how do you know it?s UART0 or UART1 from just the address?
+> > Some SoC?s don?t address sequentially *or* in a forward direction) - I
+> > believe it?s not exactly codified in ePAPR, not am I sure where it may be
> > otherwise, but it exists.
>
> We have different situation here. We need to know *the port number* as
diff --git a/a/content_digest b/N2/content_digest
index 1402493..40e6fee 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -17,30 +17,16 @@
"ref\0c0d531ec-9201-bfd8-e6c3-9140698b0697\@arm.com\0"
]
[
- "From\0Matt Sealey <Matt.Sealey\@arm.com>\0"
+ "From\0Matt.Sealey\@arm.com (Matt Sealey)\0"
]
[
- "Subject\0RE: [RFC PATCH 6/8] dts: coresight: Clean up the device tree graph bindings\0"
+ "Subject\0[RFC PATCH 6/8] dts: coresight: Clean up the device tree graph bindings\0"
]
[
"Date\0Wed, 13 Jun 2018 15:47:12 +0000\0"
]
[
- "To\0Suzuki Poulose <Suzuki.Poulose\@arm.com>\0"
-]
-[
- "Cc\0Rob Herring <robh\@kernel.org>",
- " linux-arm-kernel\@lists.infradead.org <linux-arm-kernel\@lists.infradead.org>",
- " mathieu.poirier\@linaro.org <mathieu.poirier\@linaro.org>",
- " Sudeep Holla <Sudeep.Holla\@arm.com>",
- " Mark Rutland <Mark.Rutland\@arm.com>",
- " frowand.list\@gmail.com <frowand.list\@gmail.com>",
- " Charles Garcia-Tobin <Charles.Garcia-Tobin\@arm.com>",
- " John Horley <John.Horley\@arm.com>",
- " mike.leach\@linaro.org <mike.leach\@linaro.org>",
- " coresight\@lists.linaro.org <coresight\@lists.linaro.org>",
- " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
- " devicetree\@vger.kernel.org <devicetree\@vger.kernel.org>\0"
+ "To\0linux-arm-kernel\@lists.infradead.org\0"
]
[
"\0000:1\0"
@@ -51,12 +37,12 @@
[
"Hi Suzuki,\n",
"\n",
- "> > Why not use \342\200\234unit\342\200\235?\n",
+ "> > Why not use ?unit??\n",
"> >\n",
"> > I believe we had this discussion years ago about numbering serial ports\n",
- "> > and sdhci (i.e. how do you know it\342\200\231s UART0 or UART1 from just the address?\n",
- "> > Some SoC\342\200\231s don\342\200\231t address sequentially *or* in a forward direction) - I\n",
- "> > believe it\342\200\231s not exactly codified in ePAPR, not am I sure where it may be\n",
+ "> > and sdhci (i.e. how do you know it?s UART0 or UART1 from just the address?\n",
+ "> > Some SoC?s don?t address sequentially *or* in a forward direction) - I\n",
+ "> > believe it?s not exactly codified in ePAPR, not am I sure where it may be\n",
"> > otherwise, but it exists.\n",
">\n",
"> We have different situation here. We need to know *the port number* as\n",
@@ -181,4 +167,4 @@
"IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you."
]
-23fc9eb2c9bbdca0b3015e2a5a7e0f870e6ce9ed9dea9c298e5e25dcfb501ca5
+fe714cdcecc5272664957c7188c1a61abf8a760e80557b23d9b4d15fbb67a16f
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.