linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yan Pashkovsky <yanpaso@gmail.com>
To: Yu Chen <yu.c.chen@intel.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Alexandra Yates <alexandra.yates@linux.intel.com>,
	Bastien Nocera <hadess@hadess.net>, Aaron Lu <aaron.lu@intel.com>,
	Zhang Rui <rui.zhang@intel.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: API for querying the resume cause
Date: Sat, 22 Aug 2015 00:09:00 +0300	[thread overview]
Message-ID: <55D7936C.9060208@gmail.com> (raw)
In-Reply-To: <9D8C9A00-9AA7-4BA1-9953-3DB1A88468D5@gmail.com>


I see that the community is awared of such problem. I would like to ask 
how to track  status of this API implementation except of receiving tons 
of emails in this mailing list?  :) My bug report was closed.  I would 
like to contact Lennart when it would be ready.

21.08.2015 06:17, Yu Chen пишет:
 > On 08/21/2015 10:07 AM, Krzysztof Kozlowski wrote:
 >> 2015-08-20 20:47 GMT+09:00 Yan Pashkovsky <yanpaso@gmail.com>:
 >>
 >> A little bit similar work from Alexandra Yates (CC-ed):
 >> Report interrupt(s) that caused system wakeup
 >> http://comments.gmane.org/gmane.linux.power-management.general/63805
 >>
 > This topic is interesting : )
 > BTW, in github.com/systemd/systemd/issues/926, Lennart is worried
 > about rtcwake unstable platforms. How about using suspend-to-idle
 > on these platforms, and leverage a timer instead of rtcwake..
 >
 > Best Regards,
 > Yu
 >>
 >>
 >> Best regards,
 >> Krzysztof
 >
 >


      parent reply	other threads:[~2015-08-21 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 11:47 API for querying the resume cause Yan Pashkovsky
2015-08-20 21:44 ` Yan Pashkovsky
2015-08-21  2:07 ` Krzysztof Kozlowski
2015-08-21  3:17   ` Yu Chen
     [not found]     ` <9D8C9A00-9AA7-4BA1-9953-3DB1A88468D5@gmail.com>
2015-08-21 21:09       ` Yan Pashkovsky [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=55D7936C.9060208@gmail.com \
    --to=yanpaso@gmail.com \
    --cc=aaron.lu@intel.com \
    --cc=alexandra.yates@linux.intel.com \
    --cc=hadess@hadess.net \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=yu.c.chen@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).