diff for duplicates of <20150218164629.GM26795@beef> diff --git a/a/1.txt b/N1/1.txt index cc8e3bf..f1275c4 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote: > Hi Mark, > -> > On Feb 18, 2015, at 17:41 , Mark Rutland <mark.rutland@arm.com> wrote: +> > On Feb 18, 2015, at 17:41 , Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote: > > > > Hi Pantelis, > > @@ -14,7 +14,7 @@ On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote: > >> > >> For details please refer to Documentation/devicetree/quirks.txt > >> -> >> Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com> +> >> Signed-off-by: Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org> > >> --- > >> Documentation/devicetree/quirks.txt | 101 ++++++++++ > >> drivers/of/dynamic.c | 358 ++++++++++++++++++++++++++++++++++++ @@ -44,7 +44,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 @@ -82,8 +82,8 @@ On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote: > > 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 @@ -94,7 +94,7 @@ On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote: > > 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. @@ -108,3 +108,7 @@ OTOH, some might argue that the bone common dtsi should just enable those nodes staticly for this case. -Matt +-- +To unsubscribe from this list: send the line "unsubscribe devicetree" in +the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N1/content_digest index 76ffad3..78d376f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,16 +2,28 @@ "ref\01424271576-1952-3-git-send-email-pantelis.antoniou@konsulko.com\0" "ref\020150218154106.GC29429@leverpostej\0" "ref\0FE61DD1C-51DA-4869-8A62-C019C3D70577@konsulko.com\0" - "From\0mporter@linaro.org (Matt Porter)\0" - "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0" + "ref\0FE61DD1C-51DA-4869-8A62-C019C3D70577-OWPKS81ov/FWk0Htik3J/w@public.gmane.org\0" + "From\0Matt Porter <mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>\0" + "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0" "Date\0Wed, 18 Feb 2015 11:46:29 -0500\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>\0" + "Cc\0Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>" + Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org> + Koen Kooi <koen-QLwJDigV5abLmq1fohREcCpxlwaOVQ5f@public.gmane.org> + Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org> + Ludovic Desroches <ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org> + Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> + Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org> + Nicolas Ferre <nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org> + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + " linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>\0" "\00:1\0" "b\0" "On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote:\n" "> Hi Mark,\n" "> \n" - "> > On Feb 18, 2015, at 17:41 , Mark Rutland <mark.rutland@arm.com> wrote:\n" + "> > On Feb 18, 2015, at 17:41 , Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org> wrote:\n" "> > \n" "> > Hi Pantelis,\n" "> > \n" @@ -24,7 +36,7 @@ "> >> \n" "> >> For details please refer to Documentation/devicetree/quirks.txt\n" "> >> \n" - "> >> Signed-off-by: Pantelis Antoniou <pantelis.antoniou@konsulko.com>\n" + "> >> Signed-off-by: Pantelis Antoniou <pantelis.antoniou-OWPKS81ov/FWk0Htik3J/w@public.gmane.org>\n" "> >> ---\n" "> >> Documentation/devicetree/quirks.txt | 101 ++++++++++\n" "> >> drivers/of/dynamic.c | 358 ++++++++++++++++++++++++++++++++++++\n" @@ -54,7 +66,7 @@ "> > each board.\n" "> > \n" "> \n" - "> That has not been the case in any kind of board I?ve worked with.\n" + "> That has not been the case in any kind of board I\342\200\231ve 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" @@ -92,8 +104,8 @@ "> > appended DTB if it's not possible to update the board configuration.\n" "> > \n" "> \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" + "> 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" "> \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" @@ -104,7 +116,7 @@ "> > hand you can't test quirks exhaustively either?\n" "> > \n" "> \n" - "> It?s one less thing to worry about. For example in the current mainline kernel\n" + "> It\342\200\231s 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" @@ -117,6 +129,10 @@ "OTOH, some might argue that the bone common dtsi should just enable those\n" "nodes staticly for this case.\n" "\n" - -Matt + "-Matt\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe devicetree\" in\n" + "the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -e7eebc7d4c7225270a16148d6fbf922d268db08731cfaa0a3351bd352a491ee8 +ce6f9dd7646304717262f47235332f807005fdd6532d31e75c1a01ecdab24048
diff --git a/a/1.txt b/N2/1.txt index cc8e3bf..4916ece 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -44,7 +44,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 @@ -82,8 +82,8 @@ On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote: > > 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 @@ -94,7 +94,7 @@ On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote: > > 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. diff --git a/a/content_digest b/N2/content_digest index 76ffad3..f63c2de 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,10 +2,21 @@ "ref\01424271576-1952-3-git-send-email-pantelis.antoniou@konsulko.com\0" "ref\020150218154106.GC29429@leverpostej\0" "ref\0FE61DD1C-51DA-4869-8A62-C019C3D70577@konsulko.com\0" - "From\0mporter@linaro.org (Matt Porter)\0" - "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0" + "From\0Matt Porter <mporter@linaro.org>\0" + "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0" "Date\0Wed, 18 Feb 2015 11:46:29 -0500\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Pantelis Antoniou <pantelis.antoniou@konsulko.com>\0" + "Cc\0Mark Rutland <mark.rutland@arm.com>" + Grant Likely <grant.likely@secretlab.ca> + 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" "\00:1\0" "b\0" "On Wed, Feb 18, 2015 at 05:53:50PM +0200, Pantelis Antoniou wrote:\n" @@ -54,7 +65,7 @@ "> > each board.\n" "> > \n" "> \n" - "> That has not been the case in any kind of board I?ve worked with.\n" + "> That has not been the case in any kind of board I\342\200\231ve 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" @@ -92,8 +103,8 @@ "> > appended DTB if it's not possible to update the board configuration.\n" "> > \n" "> \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" + "> 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" "> \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" @@ -104,7 +115,7 @@ "> > hand you can't test quirks exhaustively either?\n" "> > \n" "> \n" - "> It?s one less thing to worry about. For example in the current mainline kernel\n" + "> It\342\200\231s 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" @@ -119,4 +130,4 @@ "\n" -Matt -e7eebc7d4c7225270a16148d6fbf922d268db08731cfaa0a3351bd352a491ee8 +f5dd5e99f9a9f033605c15485330a7dad414bf1fe9ce9830a539042862ab31eb
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.