From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>,
paul@pwsan.com, rnayak@ti.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: OMAP2+: omap_device: maintain sane runtime pm status around suspend/resume
Date: Tue, 12 Nov 2013 17:10:40 -0600 [thread overview]
Message-ID: <5282B570.8020802@ti.com> (raw)
In-Reply-To: <878uwtnwfc.fsf@linaro.org>
On 11/12/2013 03:26 PM, Kevin Hilman wrote:
[..]
> Yes, the updated version looks much more sensible. Please repost in its
> own thread so it gets a better chance at broader review, and feel free
> to add
>
> Acked-by: Kevin Hilman <khilman@linaro.org>
Thanks. this is done[1]
[1] https://patchwork.kernel.org/patch/3176501/
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP2+: omap_device: maintain sane runtime pm status around suspend/resume
Date: Tue, 12 Nov 2013 17:10:40 -0600 [thread overview]
Message-ID: <5282B570.8020802@ti.com> (raw)
In-Reply-To: <878uwtnwfc.fsf@linaro.org>
On 11/12/2013 03:26 PM, Kevin Hilman wrote:
[..]
> Yes, the updated version looks much more sensible. Please repost in its
> own thread so it gets a better chance at broader review, and feel free
> to add
>
> Acked-by: Kevin Hilman <khilman@linaro.org>
Thanks. this is done[1]
[1] https://patchwork.kernel.org/patch/3176501/
--
Regards,
Nishanth Menon
WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>, <paul@pwsan.com>,
<rnayak@ti.com>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: OMAP2+: omap_device: maintain sane runtime pm status around suspend/resume
Date: Tue, 12 Nov 2013 17:10:40 -0600 [thread overview]
Message-ID: <5282B570.8020802@ti.com> (raw)
In-Reply-To: <878uwtnwfc.fsf@linaro.org>
On 11/12/2013 03:26 PM, Kevin Hilman wrote:
[..]
> Yes, the updated version looks much more sensible. Please repost in its
> own thread so it gets a better chance at broader review, and feel free
> to add
>
> Acked-by: Kevin Hilman <khilman@linaro.org>
Thanks. this is done[1]
[1] https://patchwork.kernel.org/patch/3176501/
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-11-12 23:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 20:59 [PATCH] ARM: OMAP2+: omap_device: maintain sane runtime pm status around suspend/resume Nishanth Menon
2013-11-07 20:59 ` Nishanth Menon
2013-11-07 20:59 ` Nishanth Menon
2013-11-07 23:44 ` Kevin Hilman
2013-11-07 23:44 ` Kevin Hilman
2013-11-07 23:44 ` Kevin Hilman
2013-11-08 0:08 ` Nishanth Menon
2013-11-08 0:08 ` Nishanth Menon
2013-11-08 0:38 ` Kevin Hilman
2013-11-08 0:38 ` Kevin Hilman
2013-11-11 16:23 ` Nishanth Menon
2013-11-11 16:23 ` Nishanth Menon
2013-11-11 16:23 ` Nishanth Menon
2013-11-12 21:26 ` Kevin Hilman
2013-11-12 21:26 ` Kevin Hilman
2013-11-12 21:26 ` Kevin Hilman
2013-11-12 23:10 ` Nishanth Menon [this message]
2013-11-12 23:10 ` Nishanth Menon
2013-11-12 23:10 ` Nishanth Menon
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=5282B570.8020802@ti.com \
--to=nm@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=paul@pwsan.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.