From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Jean Delvare <khali@linux-fr.org>,
LM Sensors <lm-sensors@lm-sensors.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Wei Ni <wni@nvidia.com>
Subject: Re: [lm-sensors] lm90 driver no longer working on PCs in 3.13
Date: Sun, 26 Jan 2014 22:02:16 +0000 [thread overview]
Message-ID: <52E585E8.4000100@roeck-us.net> (raw)
In-Reply-To: <20140126215354.GL11727@sirena.org.uk>
On 01/26/2014 01:53 PM, Mark Brown wrote:
> On Sun, Jan 26, 2014 at 01:40:30PM -0800, Guenter Roeck wrote:
>> On 01/26/2014 01:22 PM, Mark Brown wrote:
>
>>> What is this platform and why does it have the regulator API enabled in
>>> the first place?
>
>> It is a PC running Ubuntu. you'd have to ask the distro maintainers why they
>> turn on regulators.
>
>> config-3.8.0-26-generic:CONFIG_REGULATOR=y
>> config-3.8.0-35-generic:CONFIG_REGULATOR=y
>> config-3.11.0-13-generic:CONFIG_REGULATOR=y
>
> Oh, magic. Can you please file a bug with or otherwise talk to them
> asking them to turn that off (or contribute code to make it work)? Feel
> free to add me as a CC when you do so.
>
That means they would have to stop supporting anything that _does_ need regulators,
which doesn't make much sense to me.
I think the bug is on your side, not theirs.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: Mark Brown <broonie@kernel.org>
Cc: Jean Delvare <khali@linux-fr.org>,
LM Sensors <lm-sensors@lm-sensors.org>,
linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
Wei Ni <wni@nvidia.com>
Subject: Re: lm90 driver no longer working on PCs in 3.13
Date: Sun, 26 Jan 2014 14:02:16 -0800 [thread overview]
Message-ID: <52E585E8.4000100@roeck-us.net> (raw)
In-Reply-To: <20140126215354.GL11727@sirena.org.uk>
On 01/26/2014 01:53 PM, Mark Brown wrote:
> On Sun, Jan 26, 2014 at 01:40:30PM -0800, Guenter Roeck wrote:
>> On 01/26/2014 01:22 PM, Mark Brown wrote:
>
>>> What is this platform and why does it have the regulator API enabled in
>>> the first place?
>
>> It is a PC running Ubuntu. you'd have to ask the distro maintainers why they
>> turn on regulators.
>
>> config-3.8.0-26-generic:CONFIG_REGULATOR=y
>> config-3.8.0-35-generic:CONFIG_REGULATOR=y
>> config-3.11.0-13-generic:CONFIG_REGULATOR=y
>
> Oh, magic. Can you please file a bug with or otherwise talk to them
> asking them to turn that off (or contribute code to make it work)? Feel
> free to add me as a CC when you do so.
>
That means they would have to stop supporting anything that _does_ need regulators,
which doesn't make much sense to me.
I think the bug is on your side, not theirs.
Guenter
next prev parent reply other threads:[~2014-01-26 22:02 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-26 19:28 [lm-sensors] lm90 driver no longer working on PCs in 3.13 Guenter Roeck
2014-01-26 19:28 ` Guenter Roeck
2014-01-26 20:13 ` [lm-sensors] " Jean Delvare
2014-01-26 20:13 ` Jean Delvare
2014-01-26 20:42 ` [lm-sensors] " Mark Brown
2014-01-26 20:42 ` Mark Brown
2014-01-26 20:44 ` [lm-sensors] " Guenter Roeck
2014-01-26 20:44 ` Guenter Roeck
2014-01-26 20:49 ` [lm-sensors] " Jean Delvare
2014-01-26 20:49 ` Jean Delvare
2014-01-26 21:22 ` [lm-sensors] " Mark Brown
2014-01-26 21:22 ` Mark Brown
2014-01-26 21:40 ` [lm-sensors] " Guenter Roeck
2014-01-26 21:40 ` Guenter Roeck
2014-01-26 21:53 ` [lm-sensors] " Mark Brown
2014-01-26 21:53 ` Mark Brown
2014-01-26 22:02 ` Guenter Roeck [this message]
2014-01-26 22:02 ` Guenter Roeck
2014-01-26 23:37 ` [lm-sensors] " Mark Brown
2014-01-26 23:37 ` Mark Brown
2014-01-26 21:44 ` [lm-sensors] " Jean Delvare
2014-01-26 21:44 ` Jean Delvare
2014-01-26 23:15 ` [lm-sensors] " Mark Brown
2014-01-26 23:15 ` Mark Brown
2014-01-27 10:10 ` [lm-sensors] " Geert Uytterhoeven
2014-01-27 10:10 ` Geert Uytterhoeven
2014-01-27 13:18 ` [lm-sensors] " Mark Brown
2014-01-27 13:18 ` Mark Brown
2014-01-26 21:50 ` [lm-sensors] " Guenter Roeck
2014-01-26 21:50 ` Guenter Roeck
2014-01-26 22:04 ` [lm-sensors] " Guenter Roeck
2014-01-26 22:04 ` Guenter Roeck
2014-01-26 23:51 ` Mark Brown
2014-01-26 23:51 ` Mark Brown
2014-01-27 4:16 ` Guenter Roeck
2014-01-27 4:16 ` Guenter Roeck
2014-01-27 10:34 ` Mark Brown
2014-01-27 10:34 ` Mark Brown
2014-01-27 17:19 ` Stephen Warren
2014-01-27 17:19 ` Stephen Warren
2014-01-27 18:50 ` Guenter Roeck
2014-01-27 18:50 ` Guenter Roeck
2014-01-27 22:04 ` Jean Delvare
2014-01-27 22:04 ` Jean Delvare
2014-01-27 23:41 ` Guenter Roeck
2014-01-27 23:41 ` Guenter Roeck
2014-01-27 23:58 ` Mark Brown
2014-01-27 23:58 ` Mark Brown
2014-01-28 2:33 ` Guenter Roeck
2014-01-28 2:33 ` Guenter Roeck
2014-01-28 10:24 ` Mark Brown
2014-01-28 10:24 ` Mark Brown
2014-01-28 12:34 ` Mark Brown
2014-01-28 12:34 ` Mark Brown
2014-01-27 22:36 ` Mark Brown
2014-01-27 22:36 ` Mark Brown
2014-01-26 20:52 ` Mark Brown
2014-01-26 20:52 ` Mark Brown
2014-01-26 21:47 ` [lm-sensors] " Guenter Roeck
2014-01-26 21:47 ` Guenter Roeck
2014-01-26 22:01 ` [lm-sensors] " Mark Brown
2014-01-26 22:01 ` Mark Brown
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=52E585E8.4000100@roeck-us.net \
--to=linux@roeck-us.net \
--cc=broonie@kernel.org \
--cc=khali@linux-fr.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=wni@nvidia.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 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.