From: Guenter Roeck <linux@roeck-us.net>
To: Randy Dunlap <rdunlap@infradead.org>, linux-hwmon@vger.kernel.org
Cc: Jean Delvare <jdelvare@suse.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
Chris Healy <cphealy@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH 1/1] hwmon: Driver for temperature sensors on SATA drives
Date: Sun, 8 Dec 2019 22:00:30 -0800 [thread overview]
Message-ID: <2b77af4c-7a49-2f50-e209-2fe27bc0ed48@roeck-us.net> (raw)
In-Reply-To: <dc914b45-961c-a1d1-bc25-f6922004f6f4@infradead.org>
On 12/8/19 9:28 PM, Randy Dunlap wrote:
> Hi,
>
> On 12/8/19 9:21 PM, Guenter Roeck wrote:
>> diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
>> index 13a6b4afb4b3..4c63eb7ba96a 100644
>> --- a/drivers/hwmon/Kconfig
>> +++ b/drivers/hwmon/Kconfig
>> @@ -1346,6 +1346,16 @@ config SENSORS_RASPBERRYPI_HWMON
>> This driver can also be built as a module. If so, the module
>> will be called raspberrypi-hwmon.
>>
>> +config SENSORS_SATATEMP
>> + tristate "SATA hard disk drives with temperature sensors"
>> + depends on SCSI && ATA
>> + help
>> + If you say yes you get support for the temperature sensor on
>> + SATA hard disk drives.
>> +
>> + This driver can also be built as a module. If so, the module
>> + will be called smarttemp.
>
> Makefile seems to say satatemp.
>
Oops. Thanks for the note. Will fix.
Guenter
>> +
>> config SENSORS_SHT15
>> tristate "Sensiron humidity and temperature sensors. SHT15 and compat."
>> depends on GPIOLIB || COMPILE_TEST
>> diff --git a/drivers/hwmon/Makefile b/drivers/hwmon/Makefile
>> index 40c036ea45e6..fe55b8f76af9 100644
>> --- a/drivers/hwmon/Makefile
>> +++ b/drivers/hwmon/Makefile
>> @@ -148,6 +148,7 @@ obj-$(CONFIG_SENSORS_S3C) += s3c-hwmon.o
>> obj-$(CONFIG_SENSORS_SCH56XX_COMMON)+= sch56xx-common.o
>> obj-$(CONFIG_SENSORS_SCH5627) += sch5627.o
>> obj-$(CONFIG_SENSORS_SCH5636) += sch5636.o
>> +obj-$(CONFIG_SENSORS_SATATEMP) += satatemp.o
>> obj-$(CONFIG_SENSORS_SHT15) += sht15.o
>> obj-$(CONFIG_SENSORS_SHT21) += sht21.o
>> obj-$(CONFIG_SENSORS_SHT3x) += sht3x.o
>
>
next prev parent reply other threads:[~2019-12-09 6:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 5:21 [PATCH 0/1] Summary: hwmon driver for temperature sensors on SATA drives Guenter Roeck
2019-12-09 5:21 ` [PATCH 1/1] hwmon: Driver " Guenter Roeck
2019-12-09 5:28 ` Randy Dunlap
2019-12-09 6:00 ` Guenter Roeck [this message]
2019-12-09 17:08 ` Bart Van Assche
2019-12-09 19:20 ` Guenter Roeck
2019-12-10 16:10 ` Bart Van Assche
2019-12-12 22:33 ` Linus Walleij
2019-12-12 23:21 ` Martin K. Petersen
2019-12-13 4:18 ` Guenter Roeck
2019-12-17 2:47 ` Martin K. Petersen
2019-12-17 4:20 ` Guenter Roeck
2019-12-18 3:39 ` Martin K. Petersen
2019-12-11 4:08 ` [PATCH 0/1] Summary: hwmon driver " Martin K. Petersen
2019-12-11 5:57 ` Guenter Roeck
2019-12-17 2:35 ` Martin K. Petersen
2019-12-17 3:57 ` Guenter Roeck
2019-12-17 5:50 ` Damien Le Moal
2019-12-17 15:47 ` Guenter Roeck
2019-12-18 3:42 ` Martin K. Petersen
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=2b77af4c-7a49-2f50-e209-2fe27bc0ed48@roeck-us.net \
--to=linux@roeck-us.net \
--cc=cphealy@gmail.com \
--cc=jdelvare@suse.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rdunlap@infradead.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).