From: Hans de Goede <hdegoede@redhat•com>
To: linux-watchdog@vger•kernel.org
Cc: Wim Van Sebroeck <wim@iguana•be>,
LM Sensors <lm-sensors@lm-sensors•org>,
linux-next@vger•kernel.org, Hans de Goede <hdegoede@redhat•com>
Subject: [PATCH] hwmon/sch56xx: Depend on watchdog for watchdog core functions
Date: Thu, 24 May 2012 22:18:58 +0200 [thread overview]
Message-ID: <1337890738-26533-1-git-send-email-hdegoede@redhat.com> (raw)
Since the watchdog code in sch56xx-common now uses the watchdog core, the
Kconfig entires for the sch5627 and sch5636 should depend on WATCHDOG
being set.
Signed-off-by: Hans de Goede <hdegoede@redhat•com>
---
drivers/hwmon/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
index 8deedc1..3d16d66 100644
--- a/drivers/hwmon/Kconfig
+++ b/drivers/hwmon/Kconfig
@@ -1036,7 +1036,7 @@ config SENSORS_SCH56XX_COMMON
config SENSORS_SCH5627
tristate "SMSC SCH5627"
- depends on !PPC
+ depends on !PPC && WATCHDOG
select SENSORS_SCH56XX_COMMON
help
If you say yes here you get support for the hardware monitoring
@@ -1048,7 +1048,7 @@ config SENSORS_SCH5627
config SENSORS_SCH5636
tristate "SMSC SCH5636"
- depends on !PPC
+ depends on !PPC && WATCHDOG
select SENSORS_SCH56XX_COMMON
help
SMSC SCH5636 Super I/O chips include an embedded microcontroller for
--
1.7.10
next reply other threads:[~2012-05-24 20:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 20:18 Hans de Goede [this message]
2012-05-24 20:54 ` [PATCH] hwmon/sch56xx: Depend on watchdog for watchdog core functions Wim Van Sebroeck
2012-05-29 16:11 ` [lm-sensors] " Guenter Roeck
2012-05-29 17:24 ` Wim Van Sebroeck
2012-06-01 13:37 ` [lm-sensors] " Hans de Goede
2012-06-01 14:06 ` Jean Delvare
2012-06-01 15:25 ` Guenter Roeck
2012-06-06 10:29 ` Wim Van Sebroeck
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=1337890738-26533-1-git-send-email-hdegoede@redhat.com \
--to=hdegoede@redhat$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-watchdog@vger$(echo .)kernel.org \
--cc=lm-sensors@lm-sensors$(echo .)org \
--cc=wim@iguana$(echo .)be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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