From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ARM: OMAP: few more PM fixes for v3.5-rc
Date: Mon, 2 Jul 2012 05:10:04 -0700 [thread overview]
Message-ID: <20120702121004.GH1122@atomide.com> (raw)
In-Reply-To: <1340902892-9542-1-git-send-email-khilman@ti.com>
* Kevin Hilman <khilman@ti.com> [120628 10:06]:
> Tony, here are hopefully the last couple PM-related fixes for v3.5-rc.
>
> Both of these fix suspend/resume/wakeup problems on OMAP3 or OMAP4.
Thanks applying into fixes.
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP: few more PM fixes for v3.5-rc
Date: Mon, 2 Jul 2012 05:10:04 -0700 [thread overview]
Message-ID: <20120702121004.GH1122@atomide.com> (raw)
In-Reply-To: <1340902892-9542-1-git-send-email-khilman@ti.com>
* Kevin Hilman <khilman@ti.com> [120628 10:06]:
> Tony, here are hopefully the last couple PM-related fixes for v3.5-rc.
>
> Both of these fix suspend/resume/wakeup problems on OMAP3 or OMAP4.
Thanks applying into fixes.
Tony
next prev parent reply other threads:[~2012-07-02 12:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 17:01 [PATCH 0/2] ARM: OMAP: few more PM fixes for v3.5-rc Kevin Hilman
2012-06-28 17:01 ` Kevin Hilman
2012-06-28 17:01 ` [PATCH 1/2] ARM: OMAP2: Overo: init I2C before MMC to fix MMC suspend/resume failure Kevin Hilman
2012-06-28 17:01 ` Kevin Hilman
2012-06-29 6:33 ` Shubhrajyoti
2012-06-29 6:33 ` Shubhrajyoti
2012-06-28 17:01 ` [PATCH 2/2] ARM: OMAP4: TWL6030: ensure sys_nirq1 is mux'd and wakeup enabled Kevin Hilman
2012-06-28 17:01 ` Kevin Hilman
2012-07-02 12:10 ` Tony Lindgren [this message]
2012-07-02 12:10 ` [PATCH 0/2] ARM: OMAP: few more PM fixes for v3.5-rc 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=20120702121004.GH1122@atomide.com \
--to=tony@atomide.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.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 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.