From: Leo Li <pku.leo@gmail.com>
To: Rob Herring <robh@kernel.org>, rui.zhang@intel.com
Cc: Jia Hongtao <hongtao.jia@nxp.com>,
devicetree@vger.kernel.org,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
lkml <linux-kernel@vger.kernel.org>,
Scott Wood <scott.wood@nxp.com>,
Eduardo Valentin <edubezval@gmail.com>,
Kumar Gala <galak@codeaurora.org>,
Shawn Guo <shawnguo@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V2 1/7] dt-bindings: Update QorIQ TMU thermal bindings
Date: Wed, 14 Sep 2016 11:40:46 -0500 [thread overview]
Message-ID: <CADRPPNQ+hikr1qNK1wPbLnhudUrU1bN_2iuYyRQnqCN4Zwh83Q@mail.gmail.com> (raw)
In-Reply-To: <20160608195241.GA6805@rob-hp-laptop>
On Wed, Jun 8, 2016 at 2:52 PM, Rob Herring <robh@kernel.org> wrote:
> On Tue, Jun 07, 2016 at 11:27:34AM +0800, Jia Hongtao wrote:
>> For different types of SoC the sensor id and endianness may vary.
>> "#thermal-sensor-cells" is used to provide sensor id information.
>> "little-endian" property is to tell the endianness of TMU.
>>
>> Signed-off-by: Jia Hongtao <hongtao.jia@nxp.com>
>> ---
>> Changes for V2:
>> * Remove formatting chnages.
>>
>> Documentation/devicetree/bindings/thermal/qoriq-thermal.txt | 7 +++++++
>> 1 file changed, 7 insertions(+)
>
> Acked-by: Rob Herring <robh@kernel.org>
Hi Zhang Rui,
Since you have applied the driver patch, can you also apply the
binding patch? The binding is supposed to go with the driver.
Regards,
Leo
next prev parent reply other threads:[~2016-09-14 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 3:27 [PATCH V2 1/7] dt-bindings: Update QorIQ TMU thermal bindings Jia Hongtao
2016-06-08 19:52 ` Rob Herring
2016-09-14 16:40 ` Leo Li [this message]
2016-09-19 2:44 ` Zhang Rui
2016-10-09 7:12 ` Troy Jia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADRPPNQ+hikr1qNK1wPbLnhudUrU1bN_2iuYyRQnqCN4Zwh83Q@mail.gmail.com \
--to=pku.leo@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=edubezval@gmail.com \
--cc=galak@codeaurora.org \
--cc=hongtao.jia@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.com \
--cc=scott.wood@nxp.com \
--cc=shawnguo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).