All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@linaro.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: Nishanth Menon <nm@ti.com>, Tony Lindgren <tony@atomide.com>,
	linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Taras Kondratiuk <taras.kondratiuk@linaro.org>
Subject: Re: [PATCH] ARM: OMAP4+: move errata initialization to omap4_pm_init_early
Date: Thu, 23 Jan 2014 09:53:32 -0800	[thread overview]
Message-ID: <874n4uy483.fsf@paris.lan> (raw)
In-Reply-To: <52E139C5.3090207@ti.com> (Grygorii Strashko's message of "Thu, 23 Jan 2014 17:48:21 +0200")

Grygorii Strashko <grygorii.strashko@ti.com> writes:

> On 01/20/2014 10:06 PM, Nishanth Menon wrote:
>> Move all OMAP4 PM errata initializations to centralized location in
>> omap4_pm_init_early. This allows for users to utilize the erratas
>> in various submodules as needed.
>> 
> Tested-by: Grygorii Strashko <grygorii.strashko@ti.com>
>
> This patch fixes build failure caused by patch 
> https://patchwork.kernel.org/patch/3084521/ 
> in case if SMP is not enabled.

So does that mean that that patch can now be applied as is?

We could sure use that fix (or equivalent) for CPUidle breakage on 4460.

Kevin

WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: OMAP4+: move errata initialization to omap4_pm_init_early
Date: Thu, 23 Jan 2014 09:53:32 -0800	[thread overview]
Message-ID: <874n4uy483.fsf@paris.lan> (raw)
In-Reply-To: <52E139C5.3090207@ti.com> (Grygorii Strashko's message of "Thu, 23 Jan 2014 17:48:21 +0200")

Grygorii Strashko <grygorii.strashko@ti.com> writes:

> On 01/20/2014 10:06 PM, Nishanth Menon wrote:
>> Move all OMAP4 PM errata initializations to centralized location in
>> omap4_pm_init_early. This allows for users to utilize the erratas
>> in various submodules as needed.
>> 
> Tested-by: Grygorii Strashko <grygorii.strashko@ti.com>
>
> This patch fixes build failure caused by patch 
> https://patchwork.kernel.org/patch/3084521/ 
> in case if SMP is not enabled.

So does that mean that that patch can now be applied as is?

We could sure use that fix (or equivalent) for CPUidle breakage on 4460.

Kevin

  reply	other threads:[~2014-01-23 17:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1382467484-16957-1-git-send-email-grygorii.strashko@ti.com>
2013-10-22 19:07 ` [PATCH v2] ARM: OMAP4460: cpuidle: Extend PM_OMAP4_ROM_SMP_BOOT_ERRATUM_GICD on cpuidle Grygorii Strashko
2013-10-22 19:07   ` Grygorii Strashko
2013-11-14 18:35   ` Tony Lindgren
2013-11-14 18:35     ` Tony Lindgren
2013-11-15 15:36     ` Tony Lindgren
2013-11-15 15:36       ` Tony Lindgren
2013-11-15 16:02       ` Taras Kondratiuk
2013-11-15 16:02         ` Taras Kondratiuk
2013-11-15 16:11         ` Tony Lindgren
2013-11-15 16:11           ` Tony Lindgren
2013-11-15 16:12           ` Santosh Shilimkar
2013-11-15 16:12             ` Santosh Shilimkar
2014-01-14 21:26             ` Kevin Hilman
2014-01-14 21:26               ` Kevin Hilman
2014-01-14 23:28               ` Santosh Shilimkar
2014-01-14 23:28                 ` Santosh Shilimkar
2014-01-14 23:28                 ` Santosh Shilimkar
2014-01-20 20:06               ` [PATCH] ARM: OMAP4+: move errata initialization to omap4_pm_init_early Nishanth Menon
2014-01-20 20:06                 ` Nishanth Menon
2014-01-23 15:48                 ` Grygorii Strashko
2014-01-23 15:48                   ` Grygorii Strashko
2014-01-23 17:53                   ` Kevin Hilman [this message]
2014-01-23 17:53                     ` Kevin Hilman
2014-01-23 18:49                     ` Tony Lindgren
2014-01-23 18:49                       ` Tony Lindgren
2014-01-27 20:30                       ` Kevin Hilman
2014-01-27 20:30                         ` 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=874n4uy483.fsf@paris.lan \
    --to=khilman@linaro.org \
    --cc=grygorii.strashko@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=santosh.shilimkar@ti.com \
    --cc=taras.kondratiuk@linaro.org \
    --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.