diff for duplicates of <20210527025836.GD9971@aspeedtech.com>

diff --git a/a/1.txt b/N1/1.txt
index c81daf8..9b26c6c 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -30,13 +30,13 @@ rename sgpio to sgpiom as it is the driver for sgpio master interface.
 Since Andrew also point out the compatibility issues, I will modify driver
 to keep the original design.
 
-> > +? max-ngpios:
-> > +??? description:
-> > +????? represents the number of actual hardware-supported GPIOs (ie,
-> > +????? slots within the clocked serial GPIO data). Since each HW GPIO is both an
-> > +????? input and an output, we provide max_ngpios * 2 lines on our gpiochip
-> > +????? device. We also use it to define the split between the inputs and
-> > +????? outputs; the inputs start at line 0, the outputs start at max_ngpios.
+> > +  max-ngpios:
+> > +    description:
+> > +      represents the number of actual hardware-supported GPIOs (ie,
+> > +      slots within the clocked serial GPIO data). Since each HW GPIO is both an
+> > +      input and an output, we provide max_ngpios * 2 lines on our gpiochip
+> > +      device. We also use it to define the split between the inputs and
+> > +      outputs; the inputs start at line 0, the outputs start at max_ngpios.
 > 
 > Most of this description is better suited to the ngpios property, which
 > controls the number of lines that the gpiochip will expose.
@@ -61,8 +61,8 @@ to keep the original design.
 
 I will modify the description as you suggested.
 
-> > +??? minimum: 0
-> > +??? maximum: 128
+> > +    minimum: 0
+> > +    maximum: 128
 > 
 > Will this be the case for all (future) hardware? Can we leave this
 > unbound?
diff --git a/a/content_digest b/N1/content_digest
index 635d81b..8748b7c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,9 +2,22 @@
  "ref\020210526094609.14068-2-steven_lee@aspeedtech.com\0"
  "ref\0f50dec3a8be8f8254321d22d784eba4f5a032887.camel@ozlabs.org\0"
  "From\0Steven Lee <steven_lee@aspeedtech.com>\0"
- "Subject\0[PATCH v1 1/4] dt-bindings: aspeed-sgpio: Convert txt bindings to yaml.\0"
+ "Subject\0Re: [PATCH v1 1/4] dt-bindings: aspeed-sgpio: Convert txt bindings to yaml.\0"
  "Date\0Thu, 27 May 2021 10:58:37 +0800\0"
- "To\0linux-aspeed@lists.ozlabs.org\0"
+ "To\0Jeremy Kerr <jk@ozlabs.org>\0"
+ "Cc\0Linus Walleij <linus.walleij@linaro.org>"
+  Bartosz Golaszewski <bgolaszewski@baylibre.com>
+  Rob Herring <robh+dt@kernel.org>
+  Joel Stanley <joel@jms.id.au>
+  Andrew Jeffery <andrew@aj.id.au>
+  open list:GPIO SUBSYSTEM <linux-gpio@vger.kernel.org>
+  open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS <devicetree@vger.kernel.org>
+  moderated list:ARM/ASPEED MACHINE SUPPORT <linux-arm-kernel@lists.infradead.org>
+  moderated list:ARM/ASPEED MACHINE SUPPORT <linux-aspeed@lists.ozlabs.org>
+  open list <linux-kernel@vger.kernel.org>
+  Hongweiz@ami.com <Hongweiz@ami.com>
+  Ryan Chen <ryan_chen@aspeedtech.com>
+ " Billy Tsai <billy_tsai@aspeedtech.com>\0"
  "\00:1\0"
  "b\0"
  "The 05/27/2021 09:42, Jeremy Kerr wrote:\n"
@@ -39,13 +52,13 @@
  "Since Andrew also point out the compatibility issues, I will modify driver\n"
  "to keep the original design.\n"
  "\n"
- "> > +? max-ngpios:\n"
- "> > +??? description:\n"
- "> > +????? represents the number of actual hardware-supported GPIOs (ie,\n"
- "> > +????? slots within the clocked serial GPIO data). Since each HW GPIO is both an\n"
- "> > +????? input and an output, we provide max_ngpios * 2 lines on our gpiochip\n"
- "> > +????? device. We also use it to define the split between the inputs and\n"
- "> > +????? outputs; the inputs start at line 0, the outputs start at max_ngpios.\n"
+ "> > +\302\240 max-ngpios:\n"
+ "> > +\302\240\302\240\302\240 description:\n"
+ "> > +\302\240\302\240\302\240\302\240\302\240 represents the number of actual hardware-supported GPIOs (ie,\n"
+ "> > +\302\240\302\240\302\240\302\240\302\240 slots within the clocked serial GPIO data). Since each HW GPIO is both an\n"
+ "> > +\302\240\302\240\302\240\302\240\302\240 input and an output, we provide max_ngpios * 2 lines on our gpiochip\n"
+ "> > +\302\240\302\240\302\240\302\240\302\240 device. We also use it to define the split between the inputs and\n"
+ "> > +\302\240\302\240\302\240\302\240\302\240 outputs; the inputs start at line 0, the outputs start at max_ngpios.\n"
  "> \n"
  "> Most of this description is better suited to the ngpios property, which\n"
  "> controls the number of lines that the gpiochip will expose.\n"
@@ -70,8 +83,8 @@
  "\n"
  "I will modify the description as you suggested.\n"
  "\n"
- "> > +??? minimum: 0\n"
- "> > +??? maximum: 128\n"
+ "> > +\302\240\302\240\302\240 minimum: 0\n"
+ "> > +\302\240\302\240\302\240 maximum: 128\n"
  "> \n"
  "> Will this be the case for all (future) hardware? Can we leave this\n"
  "> unbound?\n"
@@ -85,4 +98,4 @@
  "> Jeremy\n"
  >
 
-1d68cea27390f7831607fe51d8adaf5af15c0198c7978877ece8ada645779f7b
+70895d64c6e1ea77e3e19b5118ef984c27e1583770cea1332edd62a063168b0b
