linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Archit Taneja <a0393947@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Joe Woodward <jw@terrafix.co.uk>, Kevin Hilman <khilman@ti.com>,
	linux-omap@vger.kernel.org, jaswinder.singh@linaro.org
Subject: Re: 3.5-rc3: PM/DSS broken (was vdd_mpu_iva warnings)
Date: Wed, 4 Jul 2012 16:08:05 +0530	[thread overview]
Message-ID: <4FF41D0D.20403@ti.com> (raw)
In-Reply-To: <1341383330.9066.7.camel@lappyti>

On Wednesday 04 July 2012 11:58 AM, Tomi Valkeinen wrote:
> On Tue, 2012-07-03 at 16:29 +0530, Archit Taneja wrote:
>
>> Thanks for testing this out.
>>
>> I was going through Tomi's queue for the 3.6 merge window:
>>
>> git://gitorious.org/linux-omap-dss2/linux.git master
>>
>> There is a commit called:
>>
>> 2b8501d777346ce1d4fe99167e9b3c0e42aae7a8
>>
>> OMAPDSS: Use PM notifiers for system suspend
>>
>> The commit message mentions the issue you see, and seems to resolve it.
>> Could you give this a try?
>>
>> Tomi is out on vacation, and I don't know why this wasn't intended for
>> the 3.5-rcs, maybe there are still some discussion going on about this?
>
> I just missed it due to the pre-vacation hassle, I was so focused on
> getting the stuff ready for next merge window.
>
> With a quick glance to my master branch, the "OMAPDSS: Use PM notifiers
> for system suspend" looks like it could go for 3.5-rc, and also
> "OMAPDSS: fix warnings if CONFIG_PM_RUNTIME=n".
>
> Archit, can you check that both apply fine to mainline, and send them to
> Florian for 3.5-rc. And make clear they are for him, so that he doesn't
> think I'll handle them =).

Sure, will do.

Archit

      reply	other threads:[~2012-07-04 10:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 10:39 3.5-rc3: vdd_mpu_iva warnings Joe Woodward
2012-06-27 15:22 ` Joe Woodward
2012-07-02 21:18 ` Kevin Hilman
2012-07-02 21:19 ` Kevin Hilman
2012-07-03  8:37   ` 3.5-rc3: PM/DSS broken (was vdd_mpu_iva warnings) Joe Woodward
2012-07-03  8:59     ` Archit Taneja
2012-07-03  9:12       ` Joe Woodward
2012-07-03 10:59         ` Archit Taneja
2012-07-03 12:31           ` Jassi Brar
2012-07-03 13:52           ` Joe Woodward
2012-07-04 14:01             ` Kevin Hilman
2012-07-05  7:58               ` Joe Woodward
2012-07-04  6:28           ` Tomi Valkeinen
2012-07-04 10:38             ` Archit Taneja [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=4FF41D0D.20403@ti.com \
    --to=a0393947@ti.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=jw@terrafix.co.uk \
    --cc=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).