From: Guenter Roeck <linux@roeck-us.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jean Delvare <jdelvare@suse.com>,
Jaghathiswari Rankappagounder Natarajan <jaghu@google.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: aspeed: add THERMAL dependency
Date: Tue, 15 Aug 2017 07:56:21 -0700 [thread overview]
Message-ID: <20170815145621.GA18049@roeck-us.net> (raw)
In-Reply-To: <20170815144856.2059759-1-arnd@arndb.de>
On Tue, Aug 15, 2017 at 04:47:47PM +0200, Arnd Bergmann wrote:
> With CONFIG_THERMAL=m, a built-in aspeed pwm tacho driver causes
> a link error:
>
> drivers/hwmon/aspeed-pwm-tacho.o: In function `aspeed_pwm_tacho_probe':
> aspeed-pwm-tacho.c:(.text+0x7f0): undefined reference to `thermal_of_cooling_device_register'
>
> This adds a dependency similar to what other hwmon drivers use,
> ensuring that the aspeed driver cannot be built-in in this
> case but has to be a module. With THERMAL=n, we still allow building it.
>
> Fixes: 2d7a548a3eff ("drivers: hwmon: Support for ASPEED PWM/Fan tach")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Applied to hwmon-next.
Thanks,
Guenter
> ---
> drivers/hwmon/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwmon/Kconfig b/drivers/hwmon/Kconfig
> index 5ef2814345ef..5b9a61f766ac 100644
> --- a/drivers/hwmon/Kconfig
> +++ b/drivers/hwmon/Kconfig
> @@ -343,6 +343,7 @@ config SENSORS_ASB100
>
> config SENSORS_ASPEED
> tristate "ASPEED AST2400/AST2500 PWM and Fan tach driver"
> + depends on THERMAL || THERMAL=n
> select REGMAP
> help
> This driver provides support for ASPEED AST2400/AST2500 PWM
> --
> 2.9.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-hwmon" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-15 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 14:47 Arnd Bergmann
2017-08-15 14:56 ` Guenter Roeck [this message]
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=20170815145621.GA18049@roeck-us.net \
--to=linux@roeck-us.net \
--cc=arnd@arndb.de \
--cc=jaghu@google.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®