All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Zoran Markovic <zrn.markovic@gmail.com>
Cc: Anton Vorontsov <anton@enomsg.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Arve Hjonnevag <arve@android.com>,
	Todd Poynor <toddpoynor@google.com>,
	John Stultz <john.stultz@linaro.org>
Subject: Re: [RFC PATCH] pm: prevent suspend until power supply events are processed
Date: Thu, 4 Sep 2014 10:23:25 +0530	[thread overview]
Message-ID: <CAKohpomn5SUmmjs=p6DSCHv-Ec4sv_1VRjVa1NV0waUk0rpd9Q@mail.gmail.com> (raw)
In-Reply-To: <CAKohpon7Uxndqg+0JSaJEhfousitDcCvpVLx1jtNtBFHh0WatQ@mail.gmail.com>

On 4 September 2014 10:21, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>>> >> +       /* dependent power supplies (e.g. battery) may have changed
>>> >> +        * state as a result of this event, so poll again and hold
>>> >> +        * the wakeup_source until all events are processed.
>>> >> +        */

But isn't this comment still incorrect? Its not about dependent supplies
but the race between the work-handler and its enqueuing?

  reply	other threads:[~2014-09-04  4:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02 20:38 [RFC PATCH] pm: prevent suspend until power supply events are processed Zoran Markovic
2013-08-22 17:10 ` Zoran Markovic
2013-08-28  1:43 ` Anton Vorontsov
2014-09-03  4:39 ` Viresh Kumar
2014-09-03  5:05   ` Viresh Kumar
     [not found]     ` <CA+B8BG5Hf8=ki0JDeRR13Mo7QRFDmsDuEpW8ozepvCp5KsY8ZA@mail.gmail.com>
2014-09-04  4:51       ` Viresh Kumar
2014-09-04  4:53         ` Viresh Kumar [this message]
2014-09-04 16:37           ` Tc, Jenny
2014-09-09 21:53             ` Todd Poynor
2014-09-09 21:55           ` Todd Poynor

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='CAKohpomn5SUmmjs=p6DSCHv-Ec4sv_1VRjVa1NV0waUk0rpd9Q@mail.gmail.com' \
    --to=viresh.kumar@linaro.org \
    --cc=anton@enomsg.org \
    --cc=arve@android.com \
    --cc=dwmw2@infradead.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=toddpoynor@google.com \
    --cc=zrn.markovic@gmail.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.