From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Rajendra Nayak <rnayak@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
khilman@deeprootsystems.com, tony@atomide.com, paul@pwsan.com
Subject: Re: [PATCH] ARM: OMAP3: board-generic: Add missing omap3_init_late
Date: Tue, 19 Feb 2013 18:47:56 +0530 [thread overview]
Message-ID: <51237B84.7060105@ti.com> (raw)
In-Reply-To: <1361278711-17672-1-git-send-email-rnayak@ti.com>
On Tuesday 19 February 2013 06:28 PM, Rajendra Nayak wrote:
> The .init_late callback for OMAP3 has been missing for DT
> builds, which causes a lot of late PM initializations to
> be missed in turn.
>
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> ---
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP3: board-generic: Add missing omap3_init_late
Date: Tue, 19 Feb 2013 18:47:56 +0530 [thread overview]
Message-ID: <51237B84.7060105@ti.com> (raw)
In-Reply-To: <1361278711-17672-1-git-send-email-rnayak@ti.com>
On Tuesday 19 February 2013 06:28 PM, Rajendra Nayak wrote:
> The .init_late callback for OMAP3 has been missing for DT
> builds, which causes a lot of late PM initializations to
> be missed in turn.
>
> Signed-off-by: Rajendra Nayak <rnayak@ti.com>
> ---
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
next prev parent reply other threads:[~2013-02-19 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 12:58 [PATCH] ARM: OMAP3: board-generic: Add missing omap3_init_late Rajendra Nayak
2013-02-19 12:58 ` Rajendra Nayak
2013-02-19 13:17 ` Santosh Shilimkar [this message]
2013-02-19 13:17 ` Santosh Shilimkar
2013-03-04 18:00 ` Tony Lindgren
2013-03-04 18:00 ` 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=51237B84.7060105@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-arm-kernel@lists.infradead.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.