From: Florian Fainelli <f.fainelli@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>,linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,Mark Rutland
<mark.rutland@arm.com>,Jean Delvare <jdelvare@suse.com>,Jonathan
Corbet <corbet@lwn.net>,"open list:OPEN FIRMWARE AND FLATTENED
DEVICE TREE BINDINGS" <devicetree@vger.kernel.org>,"open
list:HARDWARE MONITORING" <linux-hwmon@vger.kernel.org>,"open
list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 2/2] hwmon: (lm70) Add support for TI TMP122/124
Date: Sat, 21 Jan 2017 15:11:02 -0800 [thread overview]
Message-ID: <C0A9E7E0-D4AB-4154-BC47-656F8E1FE77E@gmail.com> (raw)
In-Reply-To: <8ada15e2-2b99-02c3-e731-c469a3d6c3bf@roeck-us.net>
On January 21, 2017 12:25:21 PM PST, Guenter Roeck <linux@roeck-us.net> wrote:
>On 01/21/2017 11:20 AM, Florian Fainelli wrote:
>> Add support for Texas Instruments TMP122/124 which are nearly
>identical to
>> their TMP121/123 except that they also support programmable
>temperature
>> thresholds.
>>
>> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
>
>Applied to -next.
Thanks was fast, thanks!
>
>Any plans to add support for the thresholds ?
Yes, as mentioned in the cover letter, need to get SPI_3WIRE working with the SPI controller (spi-ep93xx) to verify the thresholds do work.
Cheers
--
Florian
next prev parent reply other threads:[~2017-01-21 23:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 19:20 [PATCH 0/2] hwmon: (lm70) Couple patches Florian Fainelli
2017-01-21 19:20 ` [PATCH 1/2] hwmon: (lm70) Utilize dev_warn instead of pr_warn Florian Fainelli
2017-01-21 20:14 ` Guenter Roeck
2017-01-23 6:43 ` Joe Perches
2017-01-23 6:56 ` Joe Perches
2017-01-23 12:00 ` Julia Lawall
2017-01-23 7:01 ` Guenter Roeck
2017-01-23 7:18 ` Julia Lawall
2017-01-21 19:20 ` [PATCH 2/2] hwmon: (lm70) Add support for TI TMP122/124 Florian Fainelli
2017-01-21 20:25 ` Guenter Roeck
2017-01-21 23:11 ` Florian Fainelli [this message]
2017-01-22 0:01 ` Guenter Roeck
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=C0A9E7E0-D4AB-4154-BC47-656F8E1FE77E@gmail.com \
--to=f.fainelli@gmail.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--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