From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] OMAP: omap_device: fix !CONFIG_SUSPEND case in _noirq handlers
Date: Mon, 12 Sep 2011 10:44:03 -0700 [thread overview]
Message-ID: <4E6E44E3.1090607@ti.com> (raw)
In-Reply-To: <4E668094.40108@ti.com>
Arnd,
On 09/06/2011 01:20 PM, Kevin Hilman wrote:
> On 09/06/2011 01:13 PM, Kevin Hilman wrote:
>> On 09/01/2011 02:57 PM, Rafael J. Wysocki wrote:
>>> On Thursday, September 01, 2011, Arnd Bergmann wrote:
>>>> On Thursday 01 September 2011 11:12:02 Kevin Hilman wrote:
>>>>> The suspend/resume _noirq handlers were #ifdef'd out in the
>>>>> !CONFIG_SUSPEND case, but were still assigned to the dev_pm_ops
>>>>> struct. Fix by defining them to NULL in the !CONFIG_SUSPEND case.
>>>>>
>>>>> Reported-by: Arnd Bergmann<arnd@arndb•de>
>>>>> Signed-off-by: Kevin Hilman<khilman@ti•com>
>>>>
>>>> Acked-by: Arnd Bergmann<arnd@arndb•de>
>>>>
>>>> Thansk for the fast response!
>>>
>>> I'll apply the patch when kernel.org is back in order.
>>>
>>
>> Tony,
>>
>> I spoke w/Rafael and due to hera being down and Rafael traveling to LPC
>> he wont be able to queue this for v3.1. Can you queue up this fix? This
>> needs to go in to v3.1-rc.
>
> For convenience, this patch is in a branch in my backup gitorious repo
> with Arnd's ack added:
>
> git://gitorious.org/khilman/linux-omap-pm.git for_3.1/pm-fixes-2
>
Can you pick this up for v3.1-rc also?
Thanks,
Kevin
prev parent reply other threads:[~2011-09-12 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 18:12 [PATCH] OMAP: omap_device: fix !CONFIG_SUSPEND case in _noirq handlers Kevin Hilman
2011-09-01 18:22 ` Arnd Bergmann
2011-09-01 21:57 ` Rafael J. Wysocki
2011-09-06 20:13 ` Kevin Hilman
2011-09-06 20:20 ` Kevin Hilman
2011-09-12 17:44 ` Kevin Hilman [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=4E6E44E3.1090607@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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