diff for duplicates of <20150323234822.GC1790@linaro.org> diff --git a/a/1.txt b/N1/1.txt index 9e14b85..dfa4df6 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -56,12 +56,12 @@ On Mon, Mar 23 2015 at 17:38 -0600, Kumar Gala wrote: >>>> Definition: shall contain "qcom,saw2". A more specific value should be >>>> one of: >>> ->>> Does “qcom,saw2” have any meaning anymore? I see we use it in some places, but not everywhere on the .dts. We also see to have the L2 just be a “qcom,saw2” node, do we expect that to change? +>>> Does ?qcom,saw2? have any meaning anymore? I see we use it in some places, but not everywhere on the .dts. We also see to have the L2 just be a ?qcom,saw2? node, do we expect that to change? >>> >> It does help match a regulator node as opposed to the specific values >> below. > ->Than we should cleanup the wording. Right now it reads such that ‘qcom,saw2’ is always required. +>Than we should cleanup the wording. Right now it reads such that ?qcom,saw2? is always required. > Ah Ok. Sure. I will respin a new patchset. @@ -92,8 +92,8 @@ Anything else? >>>> >>>> Example: >>>> ->>>> - regulator@2099000 { ->>>> + power-controller@2099000 { +>>>> - regulator at 2099000 { +>>>> + power-controller at 2099000 { >>>> compatible = "qcom,saw2"; >>>> reg = <0x02099000 0x1000>, <0x02009000 0x1000>; >>>> + regulator; diff --git a/a/content_digest b/N1/content_digest index 0323e85..3e479fc 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,21 +3,10 @@ "ref\0F7886F3F-50DF-4E1B-A6DF-5463362B2BC7@codeaurora.org\0" "ref\020150323231534.GB1790@linaro.org\0" "ref\026C515E5-5CA8-4E67-9FC4-2F87208F50C4@codeaurora.org\0" - "From\0Lina Iyer <lina.iyer@linaro.org>\0" - "Subject\0Re: [PATCH v17 01/10] ARM: qcom: Add Subsystem Power Manager (SPM) driver\0" + "From\0lina.iyer@linaro.org (Lina Iyer)\0" + "Subject\0[PATCH v17 01/10] ARM: qcom: Add Subsystem Power Manager (SPM) driver\0" "Date\0Mon, 23 Mar 2015 17:48:22 -0600\0" - "To\0Kumar Gala <galak@codeaurora.org>\0" - "Cc\0daniel.lezcano@linaro.org" - khilman@linaro.org - sboyd@codeaurora.org - linux-arm-msm@vger.kernel.org - linux-pm@vger.kernel.org - linux-arm-kernel@lists.infradead.org - lorenzo.pieralisi@arm.com - msivasub@codeaurora.org - devicetree@vger.kernel.org - agross@codeaurora.org - " Arnd Bergmann <arnd@arndb.de>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Mon, Mar 23 2015 at 17:38 -0600, Kumar Gala wrote:\n" @@ -78,12 +67,12 @@ ">>>> \tDefinition: shall contain \"qcom,saw2\". A more specific value should be\n" ">>>> \t\t one of:\n" ">>>\n" - ">>> Does \342\200\234qcom,saw2\342\200\235 have any meaning anymore? I see we use it in some places, but not everywhere on the .dts. We also see to have the L2 just be a \342\200\234qcom,saw2\342\200\235 node, do we expect that to change?\n" + ">>> Does ?qcom,saw2? have any meaning anymore? I see we use it in some places, but not everywhere on the .dts. We also see to have the L2 just be a ?qcom,saw2? node, do we expect that to change?\n" ">>>\n" ">> It does help match a regulator node as opposed to the specific values\n" ">> below.\n" ">\n" - ">Than we should cleanup the wording. Right now it reads such that \342\200\230qcom,saw2\342\200\231 is always required.\n" + ">Than we should cleanup the wording. Right now it reads such that ?qcom,saw2? is always required.\n" ">\n" "Ah Ok. Sure. I will respin a new patchset.\n" "\n" @@ -114,8 +103,8 @@ ">>>>\n" ">>>> Example:\n" ">>>>\n" - ">>>> -\tregulator@2099000 {\n" - ">>>> +\tpower-controller@2099000 {\n" + ">>>> -\tregulator at 2099000 {\n" + ">>>> +\tpower-controller at 2099000 {\n" ">>>> \t\tcompatible = \"qcom,saw2\";\n" ">>>> \t\treg = <0x02099000 0x1000>, <0x02009000 0x1000>;\n" ">>>> +\t\tregulator;\n" @@ -129,4 +118,4 @@ ">a Linux Foundation Collaborative Project\n" > -e841211e27ccdf3f8e3d8c21e971694759b9b4681e73ca2b03ff9f02c25e7210 +4cdc3c3a154dcc9f574fad66ffa6199c332e3b943d014e06757f65eb997291bc
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.