linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean-Francois Dagenais <jeff.dagenais@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, jdelvare@suse.com
Subject: Re: [PATCH v2] hwmon: max6650: add thermal cooling device capability
Date: Thu, 18 Apr 2019 17:33:13 -0400	[thread overview]
Message-ID: <41DB8327-5AE7-4A57-990C-02A94FFEFF50@gmail.com> (raw)
In-Reply-To: <20190418205008.GA13496@roeck-us.net>


> On Apr 18, 2019, at 16:50, Guenter Roeck <linux@roeck-us.net> wrote:
> 
>> normally without any errors, yet the thermal-zone I defined, which is there to
>> prevent my system from burning out, would remain incomplete (without required
>> cooling device) and yet no errors came out of the kernel.
>> 
>> I just tested it and that's exactly what's happening! Yikes.
>> 
> You would still get a warning message. Better than failing to load
> the driver completely. On top of that, this used to work before.
> Plus, you said it only happens in severe situations, ie if the kernel
> is out of memory, and in thact case there would be a traceback.
> Sorry, I don't get your point.

Ok, I see. We're having the same discussion than on the v3 submission then.

If I change the dev_err to a dev_warn, but still return 0 on
thermal_of_cooling_device_register failure, you would apply the patch. It sounds
like a compromise.

Completely failing the probe call or partially succeed it results in the same
behaviour for thermal cooling use cases. But the dev_warn definitely becomes
important though.

I will v4 with that if you agree and leave the devm_ thermal register for
another day since I agree the series might be delayed too long (or
indefinitely).

Cheers!

  reply	other threads:[~2019-04-18 21:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18 16:48 [PATCH v2] hwmon: max6650: add thermal cooling device capability Jean-Francois Dagenais
2019-04-18 17:38 ` Guenter Roeck
2019-04-18 18:02   ` Jean-Francois Dagenais
2019-04-18 18:06     ` Guenter Roeck
2019-04-18 19:54       ` Jean-Francois Dagenais
2019-04-18 20:04         ` [PATCH v3] " Jean-Francois Dagenais
2019-04-18 20:13           ` Guenter Roeck
2019-04-18 20:45             ` Jean-Francois Dagenais
2019-04-18 20:55               ` Guenter Roeck
2019-04-18 20:12         ` [PATCH v2] " Guenter Roeck
2019-04-18 20:39           ` Jean-Francois Dagenais
2019-04-18 20:50             ` Guenter Roeck
2019-04-18 21:33               ` Jean-Francois Dagenais [this message]
2019-04-18 22:02                 ` Guenter Roeck
2019-04-19  0:57                   ` [PATCH v4] " Jean-Francois Dagenais

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=41DB8327-5AE7-4A57-990C-02A94FFEFF50@gmail.com \
    --to=jeff.dagenais@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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).