diff for duplicates of <20150218163238.GG32600@odux.rfo.atmel.com>
diff --git a/a/1.txt b/N2/1.txt
index ac762cd..7ed5a5e 100644
--- a/a/1.txt
+++ b/N2/1.txt
@@ -48,7 +48,7 @@ On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote:
> > each board.
> >
>
-> That has not been the case in any kind of board I’ve worked with.
+> That has not been the case in any kind of board I?ve worked with.
>
> A special firmware image that requires a different programming step at
> the factory to select the correct DTB for each is always one more thing
@@ -101,8 +101,8 @@ As for the single zImage, we should find a way to have a single DTB.
> > appended DTB if it's not possible to update the board configuration.
> >
>
-> You’re missing the point. I can’t use the same DTB for each revision of the
-> board. Each board is similar but it’s not identical.
+> You?re missing the point. I can?t use the same DTB for each revision of the
+> board. Each board is similar but it?s not identical.
>
> >> +3. Having different DTBs/DTSs for different board revisions easily leads to
> >> +drift between versions. Since no developer is expected to have every single
@@ -113,7 +113,7 @@ As for the single zImage, we should find a way to have a single DTB.
> > hand you can't test quirks exhaustively either?
> >
>
-> It’s one less thing to worry about. For example in the current mainline kernel
+> It?s one less thing to worry about. For example in the current mainline kernel
> already there is a drift between the beaglebone white and the beaglebone black.
>
> Having the same DTS is just easier to keep things in sync.
@@ -150,7 +150,7 @@ As for the single zImage, we should find a way to have a single DTB.
> > the DTB that's useful in a debug scenario doesn't mean we have to use it
> > by default.
>
-> I don’t follow. Users need this functionality to work. I.e. pass a command
+> I don?t follow. Users need this functionality to work. I.e. pass a command
> line option to use different OPPs etc. Real world usage is messy.
>
> >
@@ -172,7 +172,7 @@ As for the single zImage, we should find a way to have a single DTB.
> >> + select-quirk = <&quirk>;
> >> +
> >> + quirk: quirk {
-> >> + fragment@0 {
+> >> + fragment at 0 {
> >> + target = <&foo>;
> >> + __overlay {
> >> + bar = <0xf00>;
@@ -193,7 +193,7 @@ As for the single zImage, we should find a way to have a single DTB.
> >> + select-quirk = <&quirk>;
> >> +
> >> + quirk: quirk {
-> >> + fragment@0 {
+> >> + fragment at 0 {
> >> + target = <&foo>;
> >> + __overlay {
> >> + bar = <0xf00>;
@@ -235,7 +235,7 @@ specific code. What were the cons to swith to per-platform method?
>
> Regards
>
-> — Pantelis
+> ? Pantelis
>
Regards
diff --git a/a/content_digest b/N2/content_digest
index 8832650..938c367 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -11,30 +11,16 @@
"ref\0FE61DD1C-51DA-4869-8A62-C019C3D70577\@konsulko.com\0"
]
[
- "From\0Ludovic Desroches <ludovic.desroches\@atmel.com>\0"
+ "From\0ludovic.desroches\@atmel.com (Ludovic Desroches)\0"
]
[
- "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0"
+ "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0"
]
[
"Date\0Wed, 18 Feb 2015 17:32:38 +0100\0"
]
[
- "To\0Pantelis Antoniou <pantelis.antoniou\@konsulko.com>\0"
-]
-[
- "Cc\0Mark Rutland <mark.rutland\@arm.com>",
- " Grant Likely <grant.likely\@secretlab.ca>",
- " Matt Porter <matt.porter\@linaro.org>",
- " Koen Kooi <koen\@dominion.thruhere.net>",
- " Guenter Roeck <linux\@roeck-us.net>",
- " Ludovic Desroches <ludovic.desroches\@atmel.com>",
- " Rob Herring <robherring2\@gmail.com>",
- " Tony Lindgren <tony\@atomide.com>",
- " Nicolas Ferre <nicolas.ferre\@atmel.com>",
- " devicetree\@vger.kernel.org <devicetree\@vger.kernel.org>",
- " linux-kernel\@vger.kernel.org <linux-kernel\@vger.kernel.org>",
- " linux-arm-kernel\@lists.infradead.org <linux-arm-kernel\@lists.infradead.org>\0"
+ "To\0linux-arm-kernel\@lists.infradead.org\0"
]
[
"\0000:1\0"
@@ -93,7 +79,7 @@
"> > each board.\n",
"> > \n",
"> \n",
- "> That has not been the case in any kind of board I\342\200\231ve worked with.\n",
+ "> That has not been the case in any kind of board I?ve worked with.\n",
"> \n",
"> A special firmware image that requires a different programming step at\n",
"> the factory to select the correct DTB for each is always one more thing\n",
@@ -146,8 +132,8 @@
"> > appended DTB if it's not possible to update the board configuration.\n",
"> > \n",
"> \n",
- "> You\342\200\231re missing the point. I can\342\200\231t use the same DTB for each revision of the\n",
- "> board. Each board is similar but it\342\200\231s not identical.\n",
+ "> You?re missing the point. I can?t use the same DTB for each revision of the\n",
+ "> board. Each board is similar but it?s not identical.\n",
"> \n",
"> >> +3. Having different DTBs/DTSs for different board revisions easily leads to\n",
"> >> +drift between versions. Since no developer is expected to have every single\n",
@@ -158,7 +144,7 @@
"> > hand you can't test quirks exhaustively either?\n",
"> > \n",
"> \n",
- "> It\342\200\231s one less thing to worry about. For example in the current mainline kernel\n",
+ "> It?s one less thing to worry about. For example in the current mainline kernel\n",
"> already there is a drift between the beaglebone white and the beaglebone black.\n",
"> \n",
"> Having the same DTS is just easier to keep things in sync.\n",
@@ -195,7 +181,7 @@
"> > the DTB that's useful in a debug scenario doesn't mean we have to use it\n",
"> > by default.\n",
"> \n",
- "> I don\342\200\231t follow. Users need this functionality to work. I.e. pass a command\n",
+ "> I don?t follow. Users need this functionality to work. I.e. pass a command\n",
"> line option to use different OPPs etc. Real world usage is messy.\n",
"> \n",
"> > \n",
@@ -217,7 +203,7 @@
"> >> + select-quirk = <&quirk>;\n",
"> >> +\n",
"> >> + quirk: quirk {\n",
- "> >> + fragment\@0 {\n",
+ "> >> + fragment at 0 {\n",
"> >> + target = <&foo>;\n",
"> >> + __overlay {\n",
"> >> + bar = <0xf00>;\n",
@@ -238,7 +224,7 @@
"> >> + select-quirk = <&quirk>;\n",
"> >> +\n",
"> >> + quirk: quirk {\n",
- "> >> + fragment\@0 {\n",
+ "> >> + fragment at 0 {\n",
"> >> + target = <&foo>;\n",
"> >> + __overlay {\n",
"> >> + bar = <0xf00>;\n",
@@ -280,7 +266,7 @@
"> \n",
"> Regards\n",
"> \n",
- "> \342\200\224 Pantelis\n",
+ "> ? Pantelis\n",
"> \n",
"\n",
"Regards\n",
@@ -288,4 +274,4 @@
"Ludovic"
]
-48df905186052b7a5c929ae96513ca2526aea5a50d21ff62fe2fbd630020233b
+86adec1c1e41b3f4a4324b872746798c394fff4bba2f59e45f37ba8c86adc079
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.