linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Sebastian Reichel <sre@kernel.org>
Cc: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/8] Remove deprecated workqueue interface users
Date: Tue, 16 Aug 2016 10:51:20 -0400	[thread overview]
Message-ID: <20160816145120.GC9516@htj.duckdns.org> (raw)
In-Reply-To: <20160816002321.ibydaw5qrkpvyx26@earth>

Hello, Sebastian.

On Tue, Aug 16, 2016 at 02:23:21AM +0200, Sebastian Reichel wrote:
> At least the charger monitoring is timing critical: Many charger
> chips must be monitored (e.g. for over-temp. events). I think
> all of them have a self-protection, or a watchdog, so they would
> actually stop charging instead of overheating, but that may result
> in system failure due to power loss. Battery monitors also include
> some temperture safety checks. So without careful case-by-case
> checking the WQ_MEM_RECLAIM should not be removed IMHO.

Thanks for the clarification.  Yeah, WQ_MEM_RECLAIM seems like the
right call.

Thanks.

-- 
tejun

      reply	other threads:[~2016-08-16 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-13 16:11 [PATCH 0/8] Remove deprecated workqueue interface users Bhaktipriya Shridhar
2016-08-13 16:16 ` [PATCH 1/8] power: abx500_chargalg: Remove deprecated create_singlethread_workqueue Bhaktipriya Shridhar
2016-08-15 22:56 ` [PATCH 0/8] Remove deprecated workqueue interface users Sebastian Reichel
2016-08-15 22:59 ` Tejun Heo
2016-08-16  0:23   ` Sebastian Reichel
2016-08-16 14:51     ` Tejun Heo [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=20160816145120.GC9516@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=bhaktipriya96@gmail.com \
    --cc=dbaryshkov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=sre@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 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).