diff for duplicates of <20140930162541.GQ28481@sonymobile.com> diff --git a/a/1.txt b/N1/1.txt index 5ec676a..54d0dd2 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -27,7 +27,7 @@ On Tue 30 Sep 09:02 PDT 2014, Kumar Gala wrote: > >>> + > >> > >> Does this really ever differ for the SoCs, and even if it does why do we need -> >> to encode it in DT. Can’t we determine it via the compatible setting? +> >> to encode it in DT. Can?t we determine it via the compatible setting? > >> > > > > The two offsets could be hard coded, especially based on the compatible. @@ -36,13 +36,13 @@ On Tue 30 Sep 09:02 PDT 2014, Kumar Gala wrote: > > of here. Also this is now "symmetric" with the smd use cases, where it > > shouldn't be hard coded. > -> I do think its worth respinning until the DT is agreed to as we shouldn’t +> I do think its worth respinning until the DT is agreed to as we shouldn?t > be changing the binding. > Correct, if there's valid reason for it. -> I’m not sure how being ‘symmetric’ with the smd use case maters if +> I?m not sure how being ?symmetric? with the smd use case maters if > we are treating this RPM support vs RPM-SMD as two different things. > diff --git a/a/content_digest b/N1/content_digest index 0e71253..e7d4efa 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,22 +3,10 @@ "ref\0334C6A04-9607-4E97-A7A7-2FEED5986E57@codeaurora.org\0" "ref\020140930152838.GN28481@sonymobile.com\0" "ref\02FC56515-E6AF-4A4D-9B04-70B4A8B2C4C7@codeaurora.org\0" - "From\0Bjorn Andersson <bjorn.andersson@sonymobile.com>\0" - "Subject\0Re: [PATCH v7 1/3] mfd: devicetree: bindings: Add Qualcomm RPM DT binding\0" + "From\0bjorn.andersson@sonymobile.com (Bjorn Andersson)\0" + "Subject\0[PATCH v7 1/3] mfd: devicetree: bindings: Add Qualcomm RPM DT binding\0" "Date\0Tue, 30 Sep 2014 09:25:42 -0700\0" - "To\0Kumar Gala <galak@codeaurora.org>\0" - "Cc\0Rob Herring <robh+dt@kernel.org>" - Mark Brown <broonie@kernel.org> - Lee Jones <lee.jones@linaro.org> - Pawel Moll <pawel.moll@arm.com> - Andy Gross <agross@codeaurora.org> - Mark Rutland <mark.rutland@arm.com> - Kevin Hilman <khilman@linaro.org> - Josh Cartwright <joshc@codeaurora.org> - 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> - " linux-arm-msm@vger.kernel.org <linux-arm-msm@vger.kernel.org>\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Tue 30 Sep 09:02 PDT 2014, Kumar Gala wrote:\n" @@ -50,7 +38,7 @@ "> >>> +\n" "> >> \n" "> >> Does this really ever differ for the SoCs, and even if it does why do we need\n" - "> >> to encode it in DT. Can\342\200\231t we determine it via the compatible setting?\n" + "> >> to encode it in DT. Can?t we determine it via the compatible setting?\n" "> >> \n" "> > \n" "> > The two offsets could be hard coded, especially based on the compatible.\n" @@ -59,13 +47,13 @@ "> > of here. Also this is now \"symmetric\" with the smd use cases, where it\n" "> > shouldn't be hard coded.\n" "> \n" - "> I do think its worth respinning until the DT is agreed to as we shouldn\342\200\231t\n" + "> I do think its worth respinning until the DT is agreed to as we shouldn?t\n" "> be changing the binding.\n" "> \n" "\n" "Correct, if there's valid reason for it.\n" "\n" - "> I\342\200\231m not sure how being \342\200\230symmetric\342\200\231 with the smd use case maters if\n" + "> I?m not sure how being ?symmetric? with the smd use case maters if\n" "> we are treating this RPM support vs RPM-SMD as two different things.\n" "> \n" "\n" @@ -75,4 +63,4 @@ "Regards,\n" Bjorn -9f629adb654d1cd14f733f01a80a6c0357d3c9bd1723fdca031755d0fccb62b0 +0365ea1792fc453ed452952a946bffbcf7887fbfebb8e9fde97cb0177106926c
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.