linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and CPUilde support.
Date: Fri, 25 Mar 2011 21:00:25 +0530	[thread overview]
Message-ID: <21ea20875f7380e0987b118cc4b3ac28@mail.gmail.com> (raw)
In-Reply-To: <87mxkjusth.fsf@ti.com>

> -----Original Message-----
> From: Kevin Hilman [mailto:khilman at ti.com]
> Sent: Friday, March 25, 2011 8:54 PM
> To: Santosh Shilimkar
> Cc: linux-omap at vger.kernel.org; Rajendra Nayak; linux-arm-
> kernel at lists.infradead.org
> Subject: Re: [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and
> CPUilde support.
>
> Hi  Santosh,
>
> Santosh Shilimkar <santosh.shilimkar@ti.com> writes:

[....]
> > I pulled your latest pm-core branch
> > ------
> > commit 61cbb3172176b84c106bf0f4c32317c472932ab5
> > Merge: d0cf394... da19719...
> > Author: Kevin Hilman <khilman@ti.com>
> > Date:   Wed Mar 23 16:33:01 2011 -0700
> >
> >     Merge branch 'for_2.6.40/pm-misc' into pm-reset
> > -----------------
> > Looks like Russell's devel branch isn't merged in pm-core.
> > I didn't find the relevant patches.
>
> hmm, you're right.  I'm actually pulling Russell's devel-stable
> branch
> not his devel branch.  I assumed they were in devel-stable as well.
>
Ok.

> > By the way the relevant ARM patches are already in mainline.
> > So if the pm-core is rebased against latest mainline, we can get
> > those changes as well.
>
> Before I rebase, I'll wait at least until -rc1 and/or Tony rebases
> to mainline.
>
Ok.

> In the mean time, can you create two branches?  One with the
> dependencies and another with the OMAP4 PM series.  After some final
> review and testing, I'll merge the latter series and by then we'll
> probably have an -rc1 baseline.
>
Will do.

Regards,
Santosh

  reply	other threads:[~2011-03-25 15:30 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 14:07 [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and CPUilde support Santosh Shilimkar
2011-03-10 14:07 ` [PATCH v2 01/19] OMAP4: PM: Add omap WakeupGen module support Santosh Shilimkar
2011-03-10 14:07 ` [PATCH v2 02/19] OMAP4: Use WARN_ON() instead of BUG_ON() with graceful exit Santosh Shilimkar
2011-03-10 14:07 ` [PATCH v2 03/19] OMAP4: PM: Export omap4_get_base*() rather than global address pointers Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 04/19] OMAP4: PM: Add SAR RAM support Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 05/19] OMAP4: PM: Add CPUX OFF mode support Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 06/19] OMAP4: PM: Initialise all the clockdomains to supported states Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 07/19] OMAP4: PM: Program CPU1 to hit OFF when off-lined Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 08/19] OMAP4: PM: CPU1 wakeup workaround from Low power modes Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 09/19] OMAP4: PM: Add GIC distributor and interface enable/disable accessory API Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 10/19] OMAP4: PM: Add GIC save/restore support Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 11/19] OMAP4: PM: Add WakeupGen " Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 12/19] OMAP4: PM: Add L2 cache lowpower support Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 13/19] OMAP4: suspend: Add MPUSS RET and OFF support Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 14/19] OMAP4: pm-debug: Add wakeup timer and debug counters Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 15/19] OMAP4: cpuidle: Basic CPUidle support Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 16/19] OMAP4: cpuidle: Add MPUSS RET OFF states Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 17/19] OMAP4: cpuidle: Switch to gptimer from twd in deeper C-states Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 18/19] OMAP4: cpuidle: Add CPU hotplug notifier and prepare() hook Santosh Shilimkar
2011-03-10 14:08 ` [PATCH v2 19/19] OMAP4: Remove un-used do_wfi() macro Santosh Shilimkar
2011-03-10 19:11 ` [PATCH v2 00/19] OMAP4: PM: Suspend, CPU-hotplug and CPUilde support Kevin Hilman
2011-03-11  1:42 ` Kevin Hilman
2011-03-11  5:52   ` Santosh Shilimkar
2011-03-11 15:52     ` Kevin Hilman
2011-03-11 17:26       ` Santosh Shilimkar
2011-03-11 17:50         ` Kevin Hilman
2011-03-11 17:58           ` Santosh Shilimkar
2011-03-11 18:03             ` Kevin Hilman
2011-03-11 18:13               ` Santosh Shilimkar
2011-03-11 19:53               ` Santosh Shilimkar
2011-03-11 12:31   ` Santosh Shilimkar
2011-03-11 15:56     ` Kevin Hilman
2011-03-11 17:06       ` Santosh Shilimkar
2011-03-24 15:09       ` Kevin Hilman
2011-03-25  7:05         ` Santosh Shilimkar
2011-03-25 15:24           ` Kevin Hilman
2011-03-25 15:30             ` Santosh Shilimkar [this message]
2011-03-28 10:47             ` Santosh Shilimkar
2011-03-28 11:02             ` Santosh Shilimkar
2011-03-28 15:56               ` Kevin Hilman
2011-03-28 16:02                 ` Santosh Shilimkar
2011-03-28 16:10                 ` Kevin Hilman

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=21ea20875f7380e0987b118cc4b3ac28@mail.gmail.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).