From: Stephen Warren <swarren@wwwdotorg.org>
To: Peter De Schrijver <pdeschrijver@nvidia.com>
Cc: linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Stephen Warren <swarren@nvidia.com>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
Mike Turquette <mturquette@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: tegra: provide dummy cpu car ops
Date: Thu, 14 Feb 2013 10:43:16 -0700 [thread overview]
Message-ID: <511D2234.8000408@wwwdotorg.org> (raw)
In-Reply-To: <1360853581-9756-1-git-send-email-pdeschrijver@nvidia.com>
On 02/14/2013 07:52 AM, Peter De Schrijver wrote:
> tegra_boot_secondary() relies on some of the car ops. This means having an
> uninitialized tegra_cpu_car_ops will lead to an early boot panic.
> Providing a dummy struct avoids this and makes adding Tegra114 clock support
> in a bisectable way a lot easier.
>
> --
>
> Stephen,
>
> Should this be a separate patch or should I make this part of new release of
> the Tegra114 clock series?
I will try and remember to apply this before the Tegra114 clock series,
although I think you're reposting that anyway, so feel free to include
this in that series to make things simpler.
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: tegra: provide dummy cpu car ops
Date: Thu, 14 Feb 2013 10:43:16 -0700 [thread overview]
Message-ID: <511D2234.8000408@wwwdotorg.org> (raw)
In-Reply-To: <1360853581-9756-1-git-send-email-pdeschrijver@nvidia.com>
On 02/14/2013 07:52 AM, Peter De Schrijver wrote:
> tegra_boot_secondary() relies on some of the car ops. This means having an
> uninitialized tegra_cpu_car_ops will lead to an early boot panic.
> Providing a dummy struct avoids this and makes adding Tegra114 clock support
> in a bisectable way a lot easier.
>
> --
>
> Stephen,
>
> Should this be a separate patch or should I make this part of new release of
> the Tegra114 clock series?
I will try and remember to apply this before the Tegra114 clock series,
although I think you're reposting that anyway, so feel free to include
this in that series to make things simpler.
next prev parent reply other threads:[~2013-02-14 17:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 14:52 [PATCH] clk: tegra: provide dummy cpu car ops Peter De Schrijver
2013-02-14 14:52 ` Peter De Schrijver
2013-02-14 14:52 ` Peter De Schrijver
2013-02-14 17:43 ` Stephen Warren [this message]
2013-02-14 17:43 ` Stephen Warren
2013-03-06 23:20 ` Andrew Chew
2013-03-06 23:20 ` Andrew Chew
2013-03-06 23:20 ` Andrew Chew
[not found] ` <643E69AA4436674C8F39DCC2C05F7638629CA50C97-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2013-03-06 23:42 ` Stephen Warren
2013-03-06 23:42 ` Stephen Warren
2013-03-06 23:42 ` Stephen Warren
[not found] ` <5137D47D.6030105-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-03-06 23:59 ` Andrew Chew
2013-03-06 23:59 ` Andrew Chew
2013-03-06 23:59 ` Andrew Chew
[not found] ` <643E69AA4436674C8F39DCC2C05F7638629CA50CC0-lR+7xdUAJVNDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2013-03-07 0:04 ` Stephen Warren
2013-03-07 0:04 ` Stephen Warren
2013-03-07 0:04 ` Stephen Warren
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=511D2234.8000408@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=swarren@nvidia.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.