From: Paul Walmsley <paul@pwsan.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Nishanth Menon <nm@ti.com>,
rnayak@ti.com, khilman@linaro.org, balbi@ti.com,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3] ARM: OMAP2+: omap_device: maintain sane runtime pm status around suspend/resume
Date: Fri, 15 Nov 2013 20:04:35 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1311152002500.25958@utopia.booyaka.com> (raw)
In-Reply-To: <20131115143736.GW10317@atomide.com>
On Fri, 15 Nov 2013, Tony Lindgren wrote:
> I can take it unless you have other fixes pending right now.
Ran a quick test with the patch applied on v3.12, results here:
http://www.pwsan.com/omap/testlogs/test_nm_omap_device_fix_v3.12-rc/20131115123132/
No other fixes queued here right now, so:
Acked-by: Paul Walmsley <paul@pwsan.com>
- Paul
WARNING: multiple messages have this Message-ID (diff)
From: paul@pwsan.com (Paul Walmsley)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V3] ARM: OMAP2+: omap_device: maintain sane runtime pm status around suspend/resume
Date: Fri, 15 Nov 2013 20:04:35 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.02.1311152002500.25958@utopia.booyaka.com> (raw)
In-Reply-To: <20131115143736.GW10317@atomide.com>
On Fri, 15 Nov 2013, Tony Lindgren wrote:
> I can take it unless you have other fixes pending right now.
Ran a quick test with the patch applied on v3.12, results here:
http://www.pwsan.com/omap/testlogs/test_nm_omap_device_fix_v3.12-rc/20131115123132/
No other fixes queued here right now, so:
Acked-by: Paul Walmsley <paul@pwsan.com>
- Paul
next prev parent reply other threads:[~2013-11-15 20:04 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 23:08 [PATCH V2] ARM: OMAP2+: omap_device: maintain sane runtime pm status around suspend/resume Nishanth Menon
2013-11-12 23:08 ` Nishanth Menon
2013-11-12 23:08 ` Nishanth Menon
2013-11-13 12:51 ` Felipe Balbi
2013-11-13 12:51 ` Felipe Balbi
2013-11-13 12:51 ` Felipe Balbi
2013-11-13 14:56 ` Nishanth Menon
2013-11-13 14:56 ` Nishanth Menon
2013-11-13 14:56 ` Nishanth Menon
2013-11-13 15:20 ` Felipe Balbi
2013-11-13 15:20 ` Felipe Balbi
2013-11-13 15:20 ` Felipe Balbi
2013-11-13 15:28 ` Nishanth Menon
2013-11-13 15:28 ` Nishanth Menon
2013-11-13 15:28 ` Nishanth Menon
2013-11-13 15:45 ` Kevin Hilman
2013-11-13 15:45 ` Kevin Hilman
2013-11-13 15:45 ` Kevin Hilman
2013-11-13 16:19 ` Nishanth Menon
2013-11-13 16:19 ` Nishanth Menon
2013-11-13 16:19 ` Nishanth Menon
2013-11-14 17:05 ` [PATCH V3] " Nishanth Menon
2013-11-14 17:05 ` Nishanth Menon
2013-11-14 17:05 ` Nishanth Menon
2013-11-14 18:55 ` Felipe Balbi
2013-11-14 18:55 ` Felipe Balbi
2013-11-14 18:55 ` Felipe Balbi
2013-11-14 19:30 ` Nishanth Menon
2013-11-14 19:30 ` Nishanth Menon
2013-11-14 19:30 ` Nishanth Menon
2013-11-15 8:07 ` Paul Walmsley
2013-11-15 8:07 ` Paul Walmsley
2013-11-15 13:30 ` Nishanth Menon
2013-11-15 13:30 ` Nishanth Menon
2013-11-15 13:30 ` Nishanth Menon
2013-11-15 14:37 ` Tony Lindgren
2013-11-15 14:37 ` Tony Lindgren
2013-11-15 20:04 ` Paul Walmsley [this message]
2013-11-15 20:04 ` Paul Walmsley
2013-11-15 22:03 ` Kevin Hilman
2013-11-15 22:03 ` Kevin Hilman
2013-11-19 11:34 ` Ulf Hansson
2013-11-19 11:34 ` Ulf Hansson
2013-11-19 11:34 ` Ulf Hansson
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=alpine.DEB.2.02.1311152002500.25958@utopia.booyaka.com \
--to=paul@pwsan.com \
--cc=balbi@ti.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=rnayak@ti.com \
--cc=tony@atomide.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.