From: Guenter Roeck <linux@roeck-us.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Jean Delvare <jdelvare@suse.com>,
Samuel Mendoza-Jonas <sam@mendozajonas.com>,
Andrew Jeffery <andrew@aj.id.au>,
"Edward A. James" <eajames@us.ibm.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: pmbus: ibm-cffps depends on LEDS_CLASS
Date: Fri, 12 Jan 2018 09:19:09 -0800 [thread overview]
Message-ID: <20180112171909.GA12748@roeck-us.net> (raw)
In-Reply-To: <20180112154926.3646202-1-arnd@arndb.de>
On Fri, Jan 12, 2018 at 04:49:00PM +0100, Arnd Bergmann wrote:
> Building without CONFIG_LEDS_CLASS causes a link failure:
>
> drivers/hwmon/pmbus/ibm-cffps.o: In function `ibm_cffps_probe':
> ibm-cffps.c:(.text+0x4f4): undefined reference to `devm_of_led_classdev_register'
>
> This adds the required dependency.
>
> Fixes: f69316d62c70 ("hwmon: (pmbus) Add IBM Common Form Factor (CFF) power supply driver")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
I wanted to let Edward decide if he wants the new dependency or conditional code
in the driver. Not having heard from him, I'll take your patch instead for now.
Thanks,
Guenter
> ---
> drivers/hwmon/pmbus/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwmon/pmbus/Kconfig b/drivers/hwmon/pmbus/Kconfig
> index 08479006c7f9..6e4298e99222 100644
> --- a/drivers/hwmon/pmbus/Kconfig
> +++ b/drivers/hwmon/pmbus/Kconfig
> @@ -39,6 +39,7 @@ config SENSORS_ADM1275
>
> config SENSORS_IBM_CFFPS
> tristate "IBM Common Form Factor Power Supply"
> + depends on LEDS_CLASS
> help
> If you say yes here you get hardware monitoring support for the IBM
> Common Form Factor power supply.
> --
> 2.9.0
>
next prev parent reply other threads:[~2018-01-12 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 15:49 [PATCH] hwmon: pmbus: ibm-cffps depends on LEDS_CLASS Arnd Bergmann
2018-01-12 17:19 ` Guenter Roeck [this message]
[not found] <ca65ed8a-ac10-641a-a8fc-e042178b7451@linux.vnet.ibm.com>
2018-01-15 15:24 ` Eddie James
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=20180112171909.GA12748@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=eajames@us.ibm.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@mendozajonas.com \
/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