linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Frodo Looijaard <frodol@dds.nl>,
	lm-sensors@lm-sensors.org, Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <eduardo.valentin@ti.com>,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH] hwmon/sensors: fix SENSORS_LM75 dependencies
Date: Tue, 7 Jan 2014 13:04:01 +0100	[thread overview]
Message-ID: <20140107130401.23bffcd2@endymion.delvare> (raw)
In-Reply-To: <52CB65DA.2010103@roeck-us.net>

Hi Guenter, Randy,

On Mon, 06 Jan 2014 18:26:34 -0800, Guenter Roeck wrote:
> On 01/06/2014 05:09 PM, Randy Dunlap wrote:
> > From: Randy Dunlap <rdunlap@infradead.org>
> >
> > Fix SENSORS_LM75 dependencies to eliminate build errors:
> >
> > drivers/built-in.o: In function `lm75_remove':
> > lm75.c:(.text+0x12bd8c): undefined reference to `thermal_zone_of_sensor_unregister'
> > drivers/built-in.o: In function `lm75_probe':
> > lm75.c:(.text+0x12c123): undefined reference to `thermal_zone_of_sensor_register'
> >
> > Add depends on THERMAL_OF since that is what provides the
> > register/unregister functions above.
> >
> > Add depends on THERMAL since THERMAL is a tristate (while THERMAL_OF
> > is a bool) and SENSORS_LM75 (tristate) needs to be limited to modular
> > builds when THERMAL=m.
> >
> > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> > ---
> >   drivers/hwmon/Kconfig |    2 ++
> >   1 file changed, 2 insertions(+)
> >
> > --- linux-next-20140106.orig/drivers/hwmon/Kconfig
> > +++ linux-next-20140106/drivers/hwmon/Kconfig
> > @@ -650,6 +650,8 @@ config SENSORS_LM73
> >   config SENSORS_LM75
> >   	tristate "National Semiconductor LM75 and compatibles"
> >   	depends on I2C
> > +	depends on THERMAL
> > +	depends on THERMAL_OF
> >   	help
> >   	  If you say yes here you get support for one common type of
> >   	  temperature sensor chip, with models including:
> >
> >
> NACK. The driver does not and must not depend on THERMAL.

Correct.

> This needs to be addressed
> in the thermal code, for example with dummy declarations if THERMAL=m but
> SENSORS_LM75=y. The functions are already declared as dummies if THERMAL_OF=n.

This won't fly I'm afraid, the number of hwmon drivers affected will
grow in the future and you certainly don't want to have to change the
generic thermal code every time a new driver is added/converted.

I've looked at the problem this morning and I will admit I do not even
understand what the problem is. In Randy's config, CONFIG_THERMAL_OF=y
so both thermal_zone_of_sensor_unregister and
thermal_zone_of_sensor_register are built-in. SENSORS_LM75=y so the
calls to these functions are built-in too. I just can't see how this
can be a problem at link time. Can anyone enlighten me?

-- 
Jean Delvare

  parent reply	other threads:[~2014-01-07 12:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06  9:40 linux-next: Tree for Jan 06 Stephen Rothwell
2014-01-06 19:51 ` linux-next: Tree for Jan 06 (hwmon/lm75.c) Randy Dunlap
2014-01-06 20:32   ` Guenter Roeck
2014-01-07  1:09     ` [PATCH] hwmon/sensors: fix SENSORS_LM75 dependencies Randy Dunlap
2014-01-07  2:26       ` Guenter Roeck
2014-01-07 11:35         ` Eduardo Valentin
2014-01-07 12:04         ` Jean Delvare [this message]
2014-01-07 12:23           ` Eduardo Valentin
2014-01-07 14:05             ` Zhang, Rui
2014-01-07 14:57               ` Eduardo Valentin
2014-01-07 15:07                 ` Jean Delvare
2014-01-07 15:28                   ` Eduardo Valentin
2014-01-07 16:10                   ` Guenter Roeck
2014-01-07 14:21             ` Jean Delvare
2014-01-07 16:33               ` Eduardo Valentin
2014-01-08  1:50                 ` Guenter Roeck
2014-01-07 18:06               ` Randy Dunlap
2014-01-08  2:02               ` Zhang Rui
2014-01-07 16:02           ` Guenter Roeck
2014-01-07 11:33     ` linux-next: Tree for Jan 06 (hwmon/lm75.c) Eduardo Valentin

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=20140107130401.23bffcd2@endymion.delvare \
    --to=khali@linux-fr.org \
    --cc=eduardo.valentin@ti.com \
    --cc=frodol@dds.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lm-sensors@lm-sensors.org \
    --cc=rdunlap@infradead.org \
    --cc=rui.zhang@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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).