From: Rob Herring <robh@kernel.org>
To: Andrea Merello <andrea.merello@gmail.com>
Cc: jic23@kernel.org, Andrea Merello <andrea.merello@gmail.com>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Colin Ian King <colin.king@canonical.com>,
Patrick Havelange <patrick.havelange@essensium.com>,
Paresh Chaudhary <paresh.chaudhary@rockwellcollins.com>,
Matt Weber <matthew.weber@rockwellcollins.com>,
Matt Ranostay <matt.ranostay@konsulko.com>,
Chuhong Yuan <hslester96@gmail.com>,
Daniel Gomez <dagmcr@gmail.com>,
linux-iio@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [v2 9/9] dt-bindings: iio: maxim_thermocouple: document new 'compatible' strings
Date: Thu, 14 Nov 2019 16:12:08 -0600 [thread overview]
Message-ID: <20191114221208.GA2764@bogus> (raw)
In-Reply-To: <20191111153517.13862-10-andrea.merello@gmail.com>
On Mon, 11 Nov 2019 16:35:17 +0100, Andrea Merello wrote:
> Now the maxim_thermocouple has new, more specific, 'compatible' strings for
> better distinguish the various supported chips.
>
> This patch updates the DT bindings documentation accordingly
>
> Cc: Hartmut Knaack <knaack.h@gmx.de>
> Cc: Lars-Peter Clausen <lars@metafoo.de>
> Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
> Cc: Colin Ian King <colin.king@canonical.com>
> Cc: Patrick Havelange <patrick.havelange@essensium.com>
> Cc: Paresh Chaudhary <paresh.chaudhary@rockwellcollins.com>
> Cc: Matt Weber <matthew.weber@rockwellcollins.com>
> Cc: Matt Ranostay <matt.ranostay@konsulko.com>
> Cc: Chuhong Yuan <hslester96@gmail.com>
> Cc: Daniel Gomez <dagmcr@gmail.com>
> Cc: linux-iio@vger.kernel.org
> Cc: Rob Herring <robh+dt@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: devicetree@vger.kernel.org
> Signed-off-by: Andrea Merello <andrea.merello@gmail.com>
> ---
> .../bindings/iio/temperature/maxim_thermocouple.txt | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-11-14 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190923121714.13672-1-andrea.merello@gmail.com>
[not found] ` <20191111153517.13862-1-andrea.merello@gmail.com>
2019-11-11 15:35 ` [v2 8/9] RFC/RFT: iio: maxim_thermocouple: add thermocouple_type sysfs attribute Andrea Merello
2019-11-16 14:51 ` Jonathan Cameron
2019-11-11 15:35 ` [v2 9/9] dt-bindings: iio: maxim_thermocouple: document new 'compatible' strings Andrea Merello
2019-11-14 22:12 ` Rob Herring [this message]
[not found] ` <20191120144756.28424-1-andrea.merello@gmail.com>
2019-11-20 14:47 ` [v3 8/9] RFC/RFT: iio: maxim_thermocouple: add thermocouple_type sysfs attribute Andrea Merello
2019-11-23 12:46 ` Jonathan Cameron
2019-11-20 14:47 ` [v3 9/9] dt-bindings: iio: maxim_thermocouple: document new 'compatible' strings Andrea Merello
2019-11-23 12:46 ` Jonathan Cameron
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=20191114221208.GA2764@bogus \
--to=robh@kernel.org \
--cc=andrea.merello@gmail.com \
--cc=colin.king@canonical.com \
--cc=dagmcr@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hslester96@gmail.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matt.ranostay@konsulko.com \
--cc=matthew.weber@rockwellcollins.com \
--cc=paresh.chaudhary@rockwellcollins.com \
--cc=patrick.havelange@essensium.com \
--cc=pmeerw@pmeerw.net \
/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).