From: Alexandra Yates <alexandra.yates@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, tglx@linutronix.de,
kristen.c.accardi@intel.com
Subject: Re: [PATCH V11] Report interrupt that caused system wakeup
Date: Wed, 16 Sep 2015 11:15:03 -0700 [thread overview]
Message-ID: <55F9B1A7.3080508@linux.intel.com> (raw)
In-Reply-To: <17197937.G4AcryW2hF@vostro.rjw.lan>
Hi Rafael,
On 09/15/2015 07:40 PM, Rafael J. Wysocki wrote:
> On Tuesday, September 15, 2015 10:32:46 AM Alexandra Yates wrote:
>> Add a sysfs attribute, /sys/power/pm_wakeup_irq, reporting the IRQ
>> number of the first wakeup interrupt (that is, the first interrupt
>> from an IRQ line armed for system wakeup) seen by the kernel during
>> the most recent system suspend/resume cycle.
>>
>> This feature will be useful for system wakeup diagnostics of
>> spurious wakeup interrupts.
>>
>> Signed-off-by: Alexandra Yates <alexandra.yates@linux.intel.com>
> I've applied this, but I needed to fix it up due to build problems.
>
> I'd rather not to that again for any of your future patches.
I'm sorry you encountered this issue. But, I built the patch before I
sent it
against linux-pm with release 2.5 and the latest as of yesterday.
I'm wondering if I'm using the wrong tree/branch? I would appreciate
you help me
understand what went wrong so that this doesn't happen again for future
patches.
> Thanks,
> Rafael
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Thank you,
<Alexandra>
next prev parent reply other threads:[~2015-09-16 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH V11]Report interrupt that caused system wakeup>
2015-09-15 17:32 ` [PATCH V11] Report interrupt that caused system wakeup Alexandra Yates
2015-09-16 2:40 ` Rafael J. Wysocki
2015-09-16 18:15 ` Alexandra Yates [this message]
2015-09-17 0:32 ` Rafael J. Wysocki
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=55F9B1A7.3080508@linux.intel.com \
--to=alexandra.yates@linux.intel.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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.