diff for duplicates of <c18b064b6b01bd547b2f03006dbf4bb6fdf9b91d.camel@codeconstruct.com.au>

diff --git a/a/1.txt b/N1/1.txt
index 70a9969..7a554a2 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,15 +1,15 @@
 Hi Ryan,
 
 > Sorry, Do you mean add in description like following??
-> ? aspeed,xfer-mode:
-> ??? description: |
-> ????? I2C bus transfer mode selection.
-> ????????? ERRATA "I2C DMA fails when DRAM bus is busy and it can not
+>   aspeed,xfer-mode:
+>     description: |
+>       I2C bus transfer mode selection.
+>           ERRATA "I2C DMA fails when DRAM bus is busy and it can not
 > take DMA write data
 > Immediately", only 1 i2c bus can be enable for DMA mode.
-> ????? - "byte": I2C bus byte transfer mode.
-> ????? - "buffered": I2C bus buffer register transfer mode.
-> ????? - "dma": I2C bus dma transfer mode (default)
+>       - "byte": I2C bus byte transfer mode.
+>       - "buffered": I2C bus buffer register transfer mode.
+>       - "dma": I2C bus dma transfer mode (default)
 
 I would suggest putting some background about the transfer mode as a
 top-level description in the binding.
@@ -38,13 +38,13 @@ Perhaps something like:
 
 > > So, it sounds like:
 > > 
-> > ?- there's no point in using byte mode, as buffer mode provides
-> > ?? equivalent functionality with fewer drawbacks (ie, less interrupt
-> > ?? load)
+> >  - there's no point in using byte mode, as buffer mode provides
+> >    equivalent functionality with fewer drawbacks (ie, less interrupt
+> >    load)
 > > 
-> > ?- this just leaves the dma and buffer modes
+> >  - this just leaves the dma and buffer modes
 > > 
-> > ?- only one controller can use dma mode
+> >  - only one controller can use dma mode
 > > 
 > > So: how about just a single boolean property to indicate "use DMA
 > > on this controller"? Something like aspeed,enable-dma? Or if DT binding
diff --git a/a/content_digest b/N1/content_digest
index 3d424da..1cbaf12 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -5,23 +5,36 @@
  "ref\0f4cb3efc9825efa582aa94bd03657b1319ff38fd.camel@codeconstruct.com.au\0"
  "ref\0SEZPR06MB52695281E21B27DB57A7B2FFF2AD9@SEZPR06MB5269.apcprd06.prod.outlook.com\0"
  "From\0Jeremy Kerr <jk@codeconstruct.com.au>\0"
- "Subject\0[PATCH v6 1/2] dt-bindings: i2c: aspeed: support for AST2600-i2cv2\0"
+ "Subject\0Re: [PATCH v6 1/2] dt-bindings: i2c: aspeed: support for AST2600-i2cv2\0"
  "Date\0Wed, 01 Mar 2023 11:23:33 +0800\0"
- "To\0linux-aspeed@lists.ozlabs.org\0"
+ "To\0Ryan Chen <ryan_chen@aspeedtech.com>"
+  Andrew Jeffery <andrew@aj.id.au>
+  Brendan Higgins <brendan.higgins@linux.dev>
+  Benjamin Herrenschmidt <benh@kernel.crashing.org>
+  Joel Stanley <joel@jms.id.au>
+  Rob Herring <robh+dt@kernel.org>
+  Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
+  Philipp Zabel <p.zabel@pengutronix.de>
+  linux-i2c@vger.kernel.org <linux-i2c@vger.kernel.org>
+  openbmc@lists.ozlabs.org <openbmc@lists.ozlabs.org>
+  devicetree@vger.kernel.org <devicetree@vger.kernel.org>
+  linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org>
+  linux-aspeed@lists.ozlabs.org <linux-aspeed@lists.ozlabs.org>
+ " linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>\0"
  "\00:1\0"
  "b\0"
  "Hi Ryan,\n"
  "\n"
  "> Sorry, Do you mean add in description like following??\n"
- "> ? aspeed,xfer-mode:\n"
- "> ??? description: |\n"
- "> ????? I2C bus transfer mode selection.\n"
- "> ????????? ERRATA \"I2C DMA fails when DRAM bus is busy and it can not\n"
+ "> \302\240 aspeed,xfer-mode:\n"
+ "> \302\240\302\240\302\240 description: |\n"
+ "> \302\240\302\240\302\240\302\240\302\240 I2C bus transfer mode selection.\n"
+ "> \302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240 ERRATA \"I2C DMA fails when DRAM bus is busy and it can not\n"
  "> take DMA write data\n"
  "> Immediately\", only 1 i2c bus can be enable for DMA mode.\n"
- "> ????? - \"byte\": I2C bus byte transfer mode.\n"
- "> ????? - \"buffered\": I2C bus buffer register transfer mode.\n"
- "> ????? - \"dma\": I2C bus dma transfer mode (default)\n"
+ "> \302\240\302\240\302\240\302\240\302\240 - \"byte\": I2C bus byte transfer mode.\n"
+ "> \302\240\302\240\302\240\302\240\302\240 - \"buffered\": I2C bus buffer register transfer mode.\n"
+ "> \302\240\302\240\302\240\302\240\302\240 - \"dma\": I2C bus dma transfer mode (default)\n"
  "\n"
  "I would suggest putting some background about the transfer mode as a\n"
  "top-level description in the binding.\n"
@@ -50,13 +63,13 @@
  "\n"
  "> > So, it sounds like:\n"
  "> > \n"
- "> > ?- there's no point in using byte mode, as buffer mode provides\n"
- "> > ?? equivalent functionality with fewer drawbacks (ie, less interrupt\n"
- "> > ?? load)\n"
+ "> > \302\240- there's no point in using byte mode, as buffer mode provides\n"
+ "> > \302\240\302\240 equivalent functionality with fewer drawbacks (ie, less interrupt\n"
+ "> > \302\240\302\240 load)\n"
  "> > \n"
- "> > ?- this just leaves the dma and buffer modes\n"
+ "> > \302\240- this just leaves the dma and buffer modes\n"
  "> > \n"
- "> > ?- only one controller can use dma mode\n"
+ "> > \302\240- only one controller can use dma mode\n"
  "> > \n"
  "> > So: how about just a single boolean property to indicate \"use DMA\n"
  "> > on this controller\"? Something like aspeed,enable-dma? Or if DT binding\n"
@@ -79,4 +92,4 @@
  "\n"
  Jeremy
 
-0ab4143df28c3f9753ccdc7e501de6a6d4a8f2ac774565df0b369c3e9e339fff
+c08565d3c2d9f5dbed773c673eb6c40c49a0dc990428b95301170adbf4d97e7a
