From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] arm: get_sp() should always be compiled
Date: Fri, 18 Feb 2011 07:17:21 +0100 [thread overview]
Message-ID: <4D5E0EF1.9000404@free.fr> (raw)
In-Reply-To: <AANLkTim_F+DpeZnnhrYcVgVi-_cZvX+wC_TqUcBL6nSX@mail.gmail.com>
Le 18/02/2011 06:42, Po-Yu Chuang a ?crit :
> Hi Albert,
>
> On Fri, Feb 18, 2011 at 1:23 AM, Albert ARIBAUD<albert.aribaud@free.fr> wrote:
>> Le 17/02/2011 13:54, Macpaul Lin a ?crit :
>>> 2011/2/17 Albert ARIBAUD<albert.aribaud@free.fr>:
>>>> Le 16/02/2011 09:54, Po-Yu Chuang a ?crit :
>>>>> From: Po-Yu Chuang<ratbert@faraday-tech.com>
>>>>>
>>>>> get_sp() was incorrectly excluded if none of
>>>>> CONFIG_SETUP_MEMORY_TAGS
>>>>> CONFIG_CMDLINE_TAG
>>>>> CONFIG_INITRD_TAG
>>>>> CONFIG_SERIAL_TAG
>>>>> CONFIG_REVISION_TAG
>>>>> were defined.
>>>>
>>>> Which board exactly requires this patch?
>>>
>>> I think it is a320evb.
>>
>> Ok. This patch indeed removes the 'get_sp' error on this board's build, but
>> as an FYI, it does not build anyway.
>
> The following patches fix all the build errors of a320evb:
> (Although it still won't work, its timer still need some fix.)
>
> [PATCH v2 1/2] power: ftpmu010: move drivers/power/ftpmu010.h to include/faraday
> [PATCH v2 2/2] arm: a320: use new ftpmu010 API
Thanks. If these receive review soon, I'll include them in my next pull
along with the ARM machine type update.
> best regards,
> Po-Yu Chuang
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-02-18 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110216081330.9BE1B1519FE@gemini.denx.de>
2011-02-16 8:54 ` [U-Boot] [PATCH v2] arm: get_sp() should always be compiled Po-Yu Chuang
2011-02-17 12:44 ` Albert ARIBAUD
2011-02-17 12:54 ` Macpaul Lin
2011-02-17 17:23 ` Albert ARIBAUD
2011-02-18 5:42 ` Po-Yu Chuang
2011-02-18 6:17 ` Albert ARIBAUD [this message]
2011-02-17 17:26 ` Albert ARIBAUD
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=4D5E0EF1.9000404@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/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.