All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20120530064641.26D383E065C@localhost>

diff --git a/a/1.txt b/N1/1.txt
index d296989..565fd31 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,7 +1,7 @@
-On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86@gmail.com> wrote:
-> On Fri, May 25, 2012 at 5:29 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
-> > On Fri, 25 May 2012 21:36:20 +0800, Dong Aisheng <b29396@freescale.com> wrote:
-> >> From: Dong Aisheng <dong.aisheng@linaro.org>
+On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
+> On Fri, May 25, 2012 at 5:29 PM, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:
+> > On Fri, 25 May 2012 21:36:20 +0800, Dong Aisheng <b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:
+> >> From: Dong Aisheng <dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
 > >>
 > >> This patch implements a standard common binding for pinctrl gpio ranges.
 > >> Each SoC can add gpio ranges through device tree by adding a gpio-maps property
@@ -15,7 +15,7 @@ On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86@gmail.com> wrote:
 > >> Then the pinctrl driver can call pinctrl_dt_add_gpio_ranges(pctldev, node)
 > >> to parse and register the gpio ranges from device tree.
 > >>
-> >> Signed-off-by: Dong Aisheng <dong.aisheng@linaro.org>
+> >> Signed-off-by: Dong Aisheng <dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
 > >> ---
 > >> Personally i'm not very satisfied with current solution due to a few reasons:
 > >> 1) i can not user standard gpio api to get gpio number
@@ -23,9 +23,9 @@ On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86@gmail.com> wrote:
 > >> sure if it can be accepted by DT maintainer.
 > >
 > > Right, as mentioned in my other email, doing it this way completely
-> > breaks the way the phandle-with-args pattern works. ??That pattern
+> > breaks the way the phandle-with-args pattern works.  That pattern
 > > depends on the phandle node to have a #-cells property telling it how
-> > many cells to process for the binding. ??Adding additional data cells
+> > many cells to process for the binding.  Adding additional data cells
 > > means the kernel is no longer able to parse multiple entries in the
 > > gpios property.
 > Hmm, it can still parse multiple entries in the gpios property except
@@ -45,8 +45,8 @@ padding.
 
 g.
 
-> > Hmmm.... I need more information about this gpio-maps property. ??How
-> > is it arranged? ??What kind of data is in it. ??Can you give some
+> > Hmmm.... I need more information about this gpio-maps property.  How
+> > is it arranged?  What kind of data is in it.  Can you give some
 > > specific examples of how hardware would be described with a gpio-maps
 > > property?
 > >
diff --git a/N1/2.hdr b/N1/2.hdr
new file mode 100644
index 0000000..4b86001
--- /dev/null
+++ b/N1/2.hdr
@@ -0,0 +1,4 @@
+Content-Type: text/plain; charset="us-ascii"
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Disposition: inline
diff --git a/N1/2.txt b/N1/2.txt
new file mode 100644
index 0000000..0fd860f
--- /dev/null
+++ b/N1/2.txt
@@ -0,0 +1,4 @@
+_______________________________________________
+devicetree-discuss mailing list
+devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
+https://lists.ozlabs.org/listinfo/devicetree-discuss
diff --git a/a/content_digest b/N1/content_digest
index 6a3edc6..c43365e 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -2,16 +2,22 @@
  "ref\01337952980-14621-6-git-send-email-b29396@freescale.com\0"
  "ref\020120526002950.062683E14F7@localhost\0"
  "ref\0CAA+hA=QT83wqe8MOi4B4xY4zTGbQPVhKxwuU_A+cPg-U3JicGw@mail.gmail.com\0"
- "From\0grant.likely@secretlab.ca (Grant Likely)\0"
- "Subject\0[PATCH v4 6/6] pinctrl: add pinctrl gpio binding support\0"
+ "ref\0CAA+hA=QT83wqe8MOi4B4xY4zTGbQPVhKxwuU_A+cPg-U3JicGw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org\0"
+ "From\0Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>\0"
+ "Subject\0Re: [PATCH v4 6/6] pinctrl: add pinctrl gpio binding support\0"
  "Date\0Wed, 30 May 2012 14:46:41 +0800\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
- "\00:1\0"
+ "To\0Dong Aisheng <dongas86-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>\0"
+ "Cc\0linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org"
+  devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
+  linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
+  rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org
+ " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org\0"
+ "\01:1\0"
  "b\0"
- "On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86@gmail.com> wrote:\n"
- "> On Fri, May 25, 2012 at 5:29 PM, Grant Likely <grant.likely@secretlab.ca> wrote:\n"
- "> > On Fri, 25 May 2012 21:36:20 +0800, Dong Aisheng <b29396@freescale.com> wrote:\n"
- "> >> From: Dong Aisheng <dong.aisheng@linaro.org>\n"
+ "On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:\n"
+ "> On Fri, May 25, 2012 at 5:29 PM, Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> wrote:\n"
+ "> > On Fri, 25 May 2012 21:36:20 +0800, Dong Aisheng <b29396-KZfg59tc24xl57MIdRCFDg@public.gmane.org> wrote:\n"
+ "> >> From: Dong Aisheng <dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>\n"
  "> >>\n"
  "> >> This patch implements a standard common binding for pinctrl gpio ranges.\n"
  "> >> Each SoC can add gpio ranges through device tree by adding a gpio-maps property\n"
@@ -25,7 +31,7 @@
  "> >> Then the pinctrl driver can call pinctrl_dt_add_gpio_ranges(pctldev, node)\n"
  "> >> to parse and register the gpio ranges from device tree.\n"
  "> >>\n"
- "> >> Signed-off-by: Dong Aisheng <dong.aisheng@linaro.org>\n"
+ "> >> Signed-off-by: Dong Aisheng <dong.aisheng-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>\n"
  "> >> ---\n"
  "> >> Personally i'm not very satisfied with current solution due to a few reasons:\n"
  "> >> 1) i can not user standard gpio api to get gpio number\n"
@@ -33,9 +39,9 @@
  "> >> sure if it can be accepted by DT maintainer.\n"
  "> >\n"
  "> > Right, as mentioned in my other email, doing it this way completely\n"
- "> > breaks the way the phandle-with-args pattern works. ??That pattern\n"
+ "> > breaks the way the phandle-with-args pattern works. \303\202\302\240That pattern\n"
  "> > depends on the phandle node to have a #-cells property telling it how\n"
- "> > many cells to process for the binding. ??Adding additional data cells\n"
+ "> > many cells to process for the binding. \303\202\302\240Adding additional data cells\n"
  "> > means the kernel is no longer able to parse multiple entries in the\n"
  "> > gpios property.\n"
  "> Hmm, it can still parse multiple entries in the gpios property except\n"
@@ -55,8 +61,8 @@
  "\n"
  "g.\n"
  "\n"
- "> > Hmmm.... I need more information about this gpio-maps property. ??How\n"
- "> > is it arranged? ??What kind of data is in it. ??Can you give some\n"
+ "> > Hmmm.... I need more information about this gpio-maps property. \303\202\302\240How\n"
+ "> > is it arranged? \303\202\302\240What kind of data is in it. \303\202\302\240Can you give some\n"
  "> > specific examples of how hardware would be described with a gpio-maps\n"
  "> > property?\n"
  "> >\n"
@@ -101,5 +107,11 @@
  "gpio-pinmux = <1 1>,   <5 1>,         <20 1>;\n"
  "\n"
  g.
+ "\01:2\0"
+ "b\0"
+ "_______________________________________________\n"
+ "devicetree-discuss mailing list\n"
+ "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org\n"
+ https://lists.ozlabs.org/listinfo/devicetree-discuss
 
-07547d87ad26415a860867c69eb6c969068ecaebf67a59ed91a932709e1e34e0
+3a1f9c7d890027272accc74e9eefbe1efc42d7d6d60c7e462b8c397f88ca6163

diff --git a/a/1.txt b/N2/1.txt
index d296989..205a857 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -23,9 +23,9 @@ On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86@gmail.com> wrote:
 > >> sure if it can be accepted by DT maintainer.
 > >
 > > Right, as mentioned in my other email, doing it this way completely
-> > breaks the way the phandle-with-args pattern works. ??That pattern
+> > breaks the way the phandle-with-args pattern works.  That pattern
 > > depends on the phandle node to have a #-cells property telling it how
-> > many cells to process for the binding. ??Adding additional data cells
+> > many cells to process for the binding.  Adding additional data cells
 > > means the kernel is no longer able to parse multiple entries in the
 > > gpios property.
 > Hmm, it can still parse multiple entries in the gpios property except
@@ -45,8 +45,8 @@ padding.
 
 g.
 
-> > Hmmm.... I need more information about this gpio-maps property. ??How
-> > is it arranged? ??What kind of data is in it. ??Can you give some
+> > Hmmm.... I need more information about this gpio-maps property.  How
+> > is it arranged?  What kind of data is in it.  Can you give some
 > > specific examples of how hardware would be described with a gpio-maps
 > > property?
 > >
diff --git a/a/content_digest b/N2/content_digest
index 6a3edc6..7542648 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -2,10 +2,17 @@
  "ref\01337952980-14621-6-git-send-email-b29396@freescale.com\0"
  "ref\020120526002950.062683E14F7@localhost\0"
  "ref\0CAA+hA=QT83wqe8MOi4B4xY4zTGbQPVhKxwuU_A+cPg-U3JicGw@mail.gmail.com\0"
- "From\0grant.likely@secretlab.ca (Grant Likely)\0"
- "Subject\0[PATCH v4 6/6] pinctrl: add pinctrl gpio binding support\0"
+ "From\0Grant Likely <grant.likely@secretlab.ca>\0"
+ "Subject\0Re: [PATCH v4 6/6] pinctrl: add pinctrl gpio binding support\0"
  "Date\0Wed, 30 May 2012 14:46:41 +0800\0"
- "To\0linux-arm-kernel@lists.infradead.org\0"
+ "To\0Dong Aisheng <dongas86@gmail.com>\0"
+ "Cc\0Dong Aisheng <b29396@freescale.com>"
+  linux-kernel@vger.kernel.org
+  linux-arm-kernel@lists.infradead.org
+  linus.walleij@stericsson.com
+  swarren@wwwdotorg.org
+  devicetree-discuss@lists.ozlabs.org
+ " rob.herring@calxeda.com\0"
  "\00:1\0"
  "b\0"
  "On Sat, 26 May 2012 09:58:06 -0700, Dong Aisheng <dongas86@gmail.com> wrote:\n"
@@ -33,9 +40,9 @@
  "> >> sure if it can be accepted by DT maintainer.\n"
  "> >\n"
  "> > Right, as mentioned in my other email, doing it this way completely\n"
- "> > breaks the way the phandle-with-args pattern works. ??That pattern\n"
+ "> > breaks the way the phandle-with-args pattern works. \302\240That pattern\n"
  "> > depends on the phandle node to have a #-cells property telling it how\n"
- "> > many cells to process for the binding. ??Adding additional data cells\n"
+ "> > many cells to process for the binding. \302\240Adding additional data cells\n"
  "> > means the kernel is no longer able to parse multiple entries in the\n"
  "> > gpios property.\n"
  "> Hmm, it can still parse multiple entries in the gpios property except\n"
@@ -55,8 +62,8 @@
  "\n"
  "g.\n"
  "\n"
- "> > Hmmm.... I need more information about this gpio-maps property. ??How\n"
- "> > is it arranged? ??What kind of data is in it. ??Can you give some\n"
+ "> > Hmmm.... I need more information about this gpio-maps property. \302\240How\n"
+ "> > is it arranged? \302\240What kind of data is in it. \302\240Can you give some\n"
  "> > specific examples of how hardware would be described with a gpio-maps\n"
  "> > property?\n"
  "> >\n"
@@ -102,4 +109,4 @@
  "\n"
  g.
 
-07547d87ad26415a860867c69eb6c969068ecaebf67a59ed91a932709e1e34e0
+19ebbc6624e323487ea4200c332e2a7bb87d77efe4f13a79380897a0fd907124

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.