diff for duplicates of <1491265953.2944.78.camel@buserror.net> diff --git a/a/1.txt b/N1/1.txt index 06d2dc0..dabe020 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -9,25 +9,25 @@ On Mon, 2017-04-03 at 19:49 +0000, Roy Pledge wrote: > > > > > > > > the shared-dma-pool usage. -> > This change is not backwards compatible. Please state that and explain -> > why that is okay. If PPC needs to not change, then the old strings and +> > This change is not backwards compatible. Please state that and explain? +> > why that is okay. If PPC needs to not change, then the old strings and? > > properties should remain, but deprecated. > I think I can make the old device trees compatible since the > "compatible" string changed without too much effort or ifdefery in the -> code. However I would like to eventually see all PPC users move to the +> code. ?However I would like to eventually see all PPC users move to the > new mode as I do believe it is more in alignment with the spirit of the > reserved-memory framework that is in the kernel. How much benefit is there to changing PPC if you have to retain the old method -anyway for compatibility? Whereas if you don't convert, you retain test +anyway for compatibility? ?Whereas if you don't convert, you retain test coverage for the old device trees, and don't have to worry about -the memblock_end_of_DRAM() questions. +the?memblock_end_of_DRAM() questions. -> Do I need to mention the old mode in the binding.txt file? +> ??Do I need to mention the old mode in the binding.txt file?? Yes. -> I'm trying to keep things clean +> ?I'm trying to keep things clean > so someone reading the binding doesn't get a headache and trying to > preserve my own sanity as we move forward with adding new features to > this driver. diff --git a/a/content_digest b/N1/content_digest index 723ee79..915c14e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,16 +2,10 @@ "ref\01490822037-6752-5-git-send-email-roy.pledge@nxp.com\0" "ref\020170403154229.mf63zeiwv5naxyrr@rob-hp-laptop\0" "ref\0VI1PR04MB32166AA6361CD6F24DBC3AAF86080@VI1PR04MB3216.eurprd04.prod.outlook.com\0" - "From\0Scott Wood <oss@buserror.net>\0" - "Subject\0Re: [RFC PATCH 4/5] dt-bindings: soc/fsl: Update reserved memory binding for QBMan\0" + "From\0oss@buserror.net (Scott Wood)\0" + "Subject\0[RFC PATCH 4/5] dt-bindings: soc/fsl: Update reserved memory binding for QBMan\0" "Date\0Mon, 03 Apr 2017 19:32:33 -0500\0" - "To\0Roy Pledge <roy.pledge@nxp.com>" - " Rob Herring <robh@kernel.org>\0" - "Cc\0robin.murphy@arm.com <robin.murphy@arm.com>" - linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> - linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> - devicetree@vger.kernel.org <devicetree@vger.kernel.org> - " Madalin-Cristian Bucur <madalin.bucur@nxp.com>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Mon, 2017-04-03 at 19:49 +0000, Roy Pledge wrote:\n" @@ -25,25 +19,25 @@ "> > \n" "> > > \n" "> > > the shared-dma-pool usage.\n" - "> > This change is not backwards compatible. Please state that and explain\302\240\n" - "> > why that is okay. If PPC needs to not change, then the old strings and\302\240\n" + "> > This change is not backwards compatible. Please state that and explain?\n" + "> > why that is okay. If PPC needs to not change, then the old strings and?\n" "> > properties should remain, but deprecated.\n" "> I think I can make the old device trees compatible since the\n" "> \"compatible\" string changed without too much effort or ifdefery in the\n" - "> code. \302\240However I would like to eventually see all PPC users move to the\n" + "> code. ?However I would like to eventually see all PPC users move to the\n" "> new mode as I do believe it is more in alignment with the spirit of the\n" "> reserved-memory framework that is in the kernel.\n" "\n" "How much benefit is there to changing PPC if you have to retain the old method\n" - "anyway for compatibility? \302\240Whereas if you don't convert, you retain test\n" + "anyway for compatibility? ?Whereas if you don't convert, you retain test\n" "coverage for the old device trees, and don't have to worry about\n" - "the\302\240memblock_end_of_DRAM() questions.\n" + "the?memblock_end_of_DRAM() questions.\n" "\n" - "> \302\240\302\240Do I need to mention the old mode in the binding.txt file?\302\240\n" + "> ??Do I need to mention the old mode in the binding.txt file??\n" "\n" "Yes.\n" "\n" - "> \302\240I'm trying to keep things clean\n" + "> ?I'm trying to keep things clean\n" "> so someone reading the binding doesn't get a headache and trying to\n" "> preserve my own sanity as we move forward with adding new features to\n" "> this driver.\n" @@ -53,4 +47,4 @@ "\n" -Scott -6cb4f6a470027f95d2c923a129ba0ed2f92e6984a44807ef4018d68e13295b42 +1d1dcb6548163185cb3fd73f2fee73ea8d035929d4b041828cb03def7c3f9e67
diff --git a/a/1.txt b/N2/1.txt index 06d2dc0..a7897fc 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -36,3 +36,8 @@ If they're sufficiently different then just describe the new and old nodes separately rather than putting a bunch of if/else clauses in there. -Scott + +-- +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/N2/content_digest index 723ee79..23e337f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,16 +2,17 @@ "ref\01490822037-6752-5-git-send-email-roy.pledge@nxp.com\0" "ref\020170403154229.mf63zeiwv5naxyrr@rob-hp-laptop\0" "ref\0VI1PR04MB32166AA6361CD6F24DBC3AAF86080@VI1PR04MB3216.eurprd04.prod.outlook.com\0" - "From\0Scott Wood <oss@buserror.net>\0" + "ref\0VI1PR04MB32166AA6361CD6F24DBC3AAF86080-mr6QIVyDiCHPlBEOArXH089NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org\0" + "From\0Scott Wood <oss-fOR+EgIDQEHk1uMJSBkQmQ@public.gmane.org>\0" "Subject\0Re: [RFC PATCH 4/5] dt-bindings: soc/fsl: Update reserved memory binding for QBMan\0" "Date\0Mon, 03 Apr 2017 19:32:33 -0500\0" - "To\0Roy Pledge <roy.pledge@nxp.com>" - " Rob Herring <robh@kernel.org>\0" - "Cc\0robin.murphy@arm.com <robin.murphy@arm.com>" - linuxppc-dev@lists.ozlabs.org <linuxppc-dev@lists.ozlabs.org> - linux-arm-kernel@lists.infradead.org <linux-arm-kernel@lists.infradead.org> - devicetree@vger.kernel.org <devicetree@vger.kernel.org> - " Madalin-Cristian Bucur <madalin.bucur@nxp.com>\0" + "To\0Roy Pledge <roy.pledge-3arQi8VN3Tc@public.gmane.org>" + " Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>\0" + "Cc\0robin.murphy-5wv7dgnIgG8@public.gmane.org <robin.murphy-5wv7dgnIgG8@public.gmane.org>" + linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org <linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org> + linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org <linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org> + devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> + " Madalin-Cristian Bucur <madalin.bucur-3arQi8VN3Tc@public.gmane.org>\0" "\00:1\0" "b\0" "On Mon, 2017-04-03 at 19:49 +0000, Roy Pledge wrote:\n" @@ -51,6 +52,11 @@ "If they're sufficiently different then just describe the new and old nodes\n" "separately rather than putting a bunch of if/else clauses in there.\n" "\n" - -Scott + "-Scott\n" + "\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 -6cb4f6a470027f95d2c923a129ba0ed2f92e6984a44807ef4018d68e13295b42 +b1a7b37d00fd28d523083aef54c398eb8ad9b09c374caf29c48f96689d9703fb
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.