From: Rob Herring <robh@kernel.org>
To: Camel Guo <camel.guo@axis.com>
Cc: linux-hwmon@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, kernel@axis.com,
Jean Delvare <jdelvare@suse.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: hwmon: Add TMP401, TMP411 and TMP43x
Date: Wed, 13 Apr 2022 13:13:00 -0500 [thread overview]
Message-ID: <YlcSrOPf45ht1njU@robh.at.kernel.org> (raw)
In-Reply-To: <20220413114014.2204623-2-camel.guo@axis.com>
On Wed, 13 Apr 2022 13:40:12 +0200, Camel Guo wrote:
> Document the TMP401, TMP411 and TMP43x device devicetree bindings
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Camel Guo <camel.guo@axis.com>
> ---
>
> Notes:
> v3:
> - Remove unneeded address-cells and size-cells;
> - Change range of ti,n-factor to [-128, 127];
> - Remove unneeded 'items' of ti,beta-compensation;
> - Got Reviewed-by from Krzysztof.
>
> v2:
> - Fix format and describe hardware properties instead of programming
> models
>
> .../devicetree/bindings/hwmon/ti,tmp401.yaml | 105 ++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 106 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/ti,tmp401.yaml
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-04-13 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 11:40 [PATCH v3 0/2] hwmon/tmp401: add support of three advanced features Camel Guo
2022-04-13 11:40 ` [PATCH v3 1/2] dt-bindings: hwmon: Add TMP401, TMP411 and TMP43x Camel Guo
2022-04-13 18:13 ` Rob Herring [this message]
2022-04-13 11:40 ` [PATCH v3 2/2] hwmon: (tmp401) Add support of three advanced features Camel Guo
2022-04-14 7:59 ` [PATCH v3 0/2] hwmon/tmp401: add " Camel Guo
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=YlcSrOPf45ht1njU@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=camel.guo@axis.com \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=kernel@axis.com \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@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).