linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-pm@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	Eduardo Valentin <eduardo.valentin@ti.com>
Subject: Re: [PATCH] x86_pkg_temp_thermal: Do not expose as a hwmon device
Date: Sun, 2 Mar 2014 18:04:52 +0100	[thread overview]
Message-ID: <20140302180452.73fa2f8a@endymion.delvare> (raw)
In-Reply-To: <53135650.3070909@roeck-us.net>

On Sun, 02 Mar 2014 08:03:28 -0800, Guenter Roeck wrote:
> On 03/02/2014 06:33 AM, Jean Delvare wrote:
> > The temperature value reported by x86_pkg_temp_thermal is already
> > reported by the coretemp driver. So, do not expose this thermal zone
> > as a hwmon device, because it would be redundant.
> >
> > Signed-off-by: Jean Delvare <jdelvare@suse.de>
> > Cc: Zhang Rui <rui.zhang@intel.com>
> > Cc: Eduardo Valentin <eduardo.valentin@ti.com>
> 
> Acked-by: Guenter Roeck <linux@roeck-us.net>
> 
> Does that make the "Fix thermal zone type" patch unnecessary ?

I think both patches are needed, as type "pkg-temp-0" is wrong anyway,
regardless of the hwmon side of things. But it is less important with
this patch applied, indeed.

> If so, this patch would be a candidate for stable.

I'm still not 100% certain we want either patch in stable. After all,
they aren't fixing any critical bug, and they change user interfaces so
they could impact some users in unpredictable ways.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2014-03-02 17:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02 14:33 [PATCH] x86_pkg_temp_thermal: Do not expose as a hwmon device Jean Delvare
2014-03-02 16:03 ` Guenter Roeck
2014-03-02 17:04   ` Jean Delvare [this message]
2014-03-02 17:44     ` Guenter Roeck
2014-03-07  8:07     ` Jean Delvare

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=20140302180452.73fa2f8a@endymion.delvare \
    --to=jdelvare@suse.de \
    --cc=eduardo.valentin@ti.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=rui.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).