public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
	Alan Stern <stern@rowland.harvard.edu>
Cc: Brian Norris <briannorris@chromium.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Len Brown <len.brown@intel.com>, Nishanth Menon <nm@ti.com>,
	Pavel Machek <pavel@ucw.cz>, Ulf Hansson <ulf.hansson@linaro.org>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org
Subject: [PATCH 0/2] Two wakeirq fixes
Date: Fri, 10 Feb 2017 14:24:59 -0800	[thread overview]
Message-ID: <20170210222501.7948-1-tony@atomide.com> (raw)

Hi all,

Here are two wakeirq fixes from Grygorii that have been pending for
a while.

Earlier before commit bed570307ed7 ("PM / wakeirq: Fix dedicated
wakeirq for drivers not using autosuspend") I did not see changes
with my test cases with these two changes, but now I have test cases
that get fixed with these two patches.

Regards,

Tony

Grygorii Strashko (2):
  PM / wakeirq: Enable dedicated wakeirq for suspend
  PM / wakeirq: Fix spurious wake-up events for dedicated wakeirqs

 drivers/base/power/wakeirq.c | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

-- 
2.11.1

             reply	other threads:[~2017-02-10 22:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 22:24 Tony Lindgren [this message]
2017-02-10 22:25 ` [PATCH 1/2] PM / wakeirq: Enable dedicated wakeirq for suspend Tony Lindgren
2017-02-10 22:25 ` [PATCH 2/2] PM / wakeirq: Fix spurious wake-up events for dedicated wakeirqs Tony Lindgren
2017-02-10 22:33 ` [PATCH 0/2] Two wakeirq fixes Rafael J. Wysocki
2017-02-10 22:37   ` Tony Lindgren

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=20170210222501.7948-1-tony@atomide.com \
    --to=tony@atomide.com \
    --cc=briannorris@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=pavel@ucw.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stern@rowland.harvard.edu \
    --cc=ulf.hansson@linaro.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