From: Chee, Tien Fong <tien.fong.chee@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: socfpga: boot0 hook: remove macro from boot0 header file
Date: Wed, 29 Mar 2017 03:36:19 +0000 [thread overview]
Message-ID: <1490758579.10114.6.camel@intel.com> (raw)
In-Reply-To: <1490758137-12858-1-git-send-email-tien.fong.chee@intel.com>
On Rab, 2017-03-29 at 11:28 +0800, tien.fong.chee at intel.com wrote:
> From: "Chee, Tien Fong" <tien.fong.chee@intel.com>
>
> Commit ce62e57fc571 ("ARM: boot0 hook: remove macro, include whole
> header file") miss out cleaning macro in this header file, and this
> has broken implementation of a boot header capability in socfpga
> SPL. Remove the macro in this file, and recovering it back
> to proper functioning.
>
Please ignore this patch, i will send out another patch. Thanks.
> Fixes: ce62e57fc571 ("ARM: boot0 hook: remove macro, include whole
> header file")
>
> Signed-off-by: Chee, Tien Fong <tien.fong.chee@intel.com>
> ---
> arch/arm/mach-socfpga/include/mach/boot0.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/arch/arm/mach-socfpga/include/mach/boot0.h
> b/arch/arm/mach-socfpga/include/mach/boot0.h
> index aaada31..40f9d32 100644
> --- a/arch/arm/mach-socfpga/include/mach/boot0.h
> +++ b/arch/arm/mach-socfpga/include/mach/boot0.h
> @@ -8,7 +8,6 @@
> #define __BOOT0_H
>
> #ifdef CONFIG_SPL_BUILD
> -#define ARM_SOC_BOOT0_HOOK
> \
> .balignl 64,0xf33db33f;
> \
>
> \
> .word 0x1337c0d3; /* SoCFPGA preloader
> validation word */ \
> @@ -20,9 +19,6 @@
> nop;
> \
> nop;
> \
> nop;
> -#else
> -#define ARM_SOC_BOOT0_HOOK
> #endif
>
> -
> #endif /* __BOOT0_H */
next prev parent reply other threads:[~2017-03-29 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 3:28 [U-Boot] [PATCH] ARM: socfpga: boot0 hook: remove macro from boot0 header file tien.fong.chee at intel.com
2017-03-29 3:36 ` Chee, Tien Fong [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-29 3:49 tien.fong.chee at intel.com
2017-03-29 9:03 ` Marek Vasut
2017-03-30 1:22 ` chee skywind
2017-03-31 11:12 ` Marek Vasut
[not found] ` <CAJ2hV_qUGm+kg9peTdPE2ew=fnFwpERrd_N3CsLcrU1cZTSx9A@mail.gmail.com>
[not found] ` <CAJ2hV_pkX=DeD3z6ymnYw5DNp-qPSzwHBvNa66ff3D=Qmh+y9Q@mail.gmail.com>
2017-04-04 1:02 ` chee skywind
2017-03-31 11:14 ` Marek Vasut
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=1490758579.10114.6.camel@intel.com \
--to=tien.fong.chee@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox