diff for duplicates of <20150218173115.GG29429@leverpostej> diff --git a/a/1.txt b/N1/1.txt index f10c787..608619d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -36,8 +36,8 @@ To some extent there must be a DTB that will work across all variants > > 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. I think you've misunderstood my point. If you program the board with the relevant DTB, or use appended DTB, then you will pass the correct DTB to @@ -55,7 +55,7 @@ its own 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. What's currently out of sync? @@ -115,7 +115,7 @@ regardless of whatever the boot-time configuration was, no? > > 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. This was all about the debug case; for anything that's required for @@ -139,7 +139,7 @@ normal operation I agree that a command line argument doesn't work. > >> + select-quirk = <&quirk>; > >> + > >> + quirk: quirk { -> >> + fragment at 0 { +> >> + fragment@0 { > >> + target = <&foo>; > >> + __overlay { > >> + bar = <0xf00>; @@ -160,7 +160,7 @@ normal operation I agree that a command line argument doesn't work. > >> + select-quirk = <&quirk>; > >> + > >> + quirk: quirk { -> >> + fragment at 0 { +> >> + fragment@0 { > >> + target = <&foo>; > >> + __overlay { > >> + bar = <0xf00>; diff --git a/a/content_digest b/N1/content_digest index 0f922f7..71c4d9a 100644 --- a/a/content_digest +++ b/N1/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\0mark.rutland@arm.com (Mark Rutland)\0" - "Subject\0[PATCH 2/4] of: DT quirks infrastructure\0" + "From\0Mark Rutland <mark.rutland@arm.com>\0" + "Subject\0Re: [PATCH 2/4] of: DT quirks infrastructure\0" "Date\0Wed, 18 Feb 2015 17:31:16 +0000\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0Pantelis Antoniou <pantelis.antoniou@konsulko.com>\0" + "Cc\0Grant 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" "\00:1\0" "b\0" "> >> +While this may in theory work, in practice it is very cumbersome\n" @@ -46,8 +57,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" "I think you've misunderstood my point. If you program the board with the\n" "relevant DTB, or use appended DTB, then you will pass the correct DTB to\n" @@ -65,7 +76,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" "What's currently out of sync?\n" @@ -125,7 +136,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?t follow. Users need this functionality to work. I.e. pass a command\n" + "> I don\342\200\231t 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" "This was all about the debug case; for anything that's required for\n" @@ -149,7 +160,7 @@ "> >> + select-quirk = <&quirk>;\n" "> >> +\n" "> >> + quirk: quirk {\n" - "> >> + fragment at 0 {\n" + "> >> + fragment@0 {\n" "> >> + target = <&foo>;\n" "> >> + __overlay {\n" "> >> + bar = <0xf00>;\n" @@ -170,7 +181,7 @@ "> >> + select-quirk = <&quirk>;\n" "> >> +\n" "> >> + quirk: quirk {\n" - "> >> + fragment at 0 {\n" + "> >> + fragment@0 {\n" "> >> + target = <&foo>;\n" "> >> + __overlay {\n" "> >> + bar = <0xf00>;\n" @@ -210,4 +221,4 @@ "Thanks,\n" Mark. -f6700f68c4beb39a3ed2bc8564dd130473dc2101471c0811073c3d2db4d36da0 +313ee339c7e28c2deda8d39252846e32d8b03bc0d5faf07d7a186289dc265ff0
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.