From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH v3] drivers/hwmon NTC Thermistor Initial
Date: Fri, 24 Dec 2010 05:42:04 +0000 [thread overview]
Message-ID: <20101224054204.GA30389@ericsson.com> (raw)
In-Reply-To: <1292842122-3992-1-git-send-email-myungjoo.ham@samsung.com>
On Thu, Dec 23, 2010 at 09:37:37PM -0500, 함명주 wrote:
>
> Sender : Guenter Roeck<guenter.roeck@ericsson.com>
> > On Thu, Dec 23, 2010 at 08:36:04PM -0500, MyungJoo Ham wrote:
> > [ ... ]
> > > >> +int ntc_thermistor_read(struct device *dev)
> > > >> +{
> > > >> + ? ? ? return _ntc_thermistor_read(dev_get_drvdata(dev));
> > > >> +}
> > > >
> > > > Function should be removed since it is no longer exported.
> > > >
> > >
> > > I have been considering to use this function at the board file in the
> > > kernel space.
> >
> > That means you would have to export the function, and we are back to square one,
> > ie you really use a hwmon driver to provide functions to a non-hwmon driver.
> >
>
> Yes, this hwmon driver is used by another (board file) when CONFIG_HWMON and
> CONFIG_NTC_.... is "y". Otherwise, the code that requires hwmon driver is not
> compiled and a dummy is used instead. Thus, we don't need EXPORT anyway.
>
After browsing through the kernel source - such a dependency on CONFIG_HWMON
would be the first in the kernel. I think such a dependency is broken, and
I won't be the one to approve it.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2010-12-24 5:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 10:48 [lm-sensors] [PATCH v3] drivers/hwmon NTC Thermistor Initial MyungJoo Ham
2010-12-23 20:34 ` Guenter Roeck
2010-12-24 1:36 ` MyungJoo Ham
2010-12-24 2:08 ` Guenter Roeck
2010-12-24 2:37 ` 함명주
2010-12-24 3:09 ` Guenter Roeck
2010-12-24 5:42 ` 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=20101224054204.GA30389@ericsson.com \
--to=guenter.roeck@ericsson.com \
--cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.