From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] arm: mvebu: Remove "u-boot.kwb" CONFIG_BUILD_TARGET for non-SPL targets
Date: Mon, 04 May 2015 17:39:20 +0200 [thread overview]
Message-ID: <554792A8.6030501@denx.de> (raw)
In-Reply-To: <CAPnjgZ0-riY27nrAdEpyYtHhPq11+HbSbXT8S7dEnLKq8wBV_w@mail.gmail.com>
Hi Simon,
On 04.05.2015 17:35, Simon Glass wrote:
> On 4 May 2015 at 09:31, Stefan Roese <sr@denx.de> wrote:
>>
>> By removing this default build target, the "u-boot.kwb" target is not
>> automatically generated. This fixes a temporary build error when using
>> out-of-tree builds, as buildman does per default (reported by Simon).
>>
>> When the full SPL support is added for these targets with the DDR training
>> code, the "u-boot-spl.kwb" image will be generated automatically.
>>
>> Users providing a special bin_hdr binary (binary.0) file can always add
>> this binary file and generate the full firmware image by issuing the
>> "make u-boot.kwb" command directly.
>>
>> Signed-off-by: Stefan Roese <sr@denx.de>
>> Cc: Simon Glass <sjg@chromium.org>
>> Cc: Prafulla Wadaskar <prafulla@marvell.com>
>> Cc: Luka Perkov <luka.perkov@sartura.hr>
>> ---
>> arch/arm/mach-mvebu/include/mach/config.h | 2 --
>> 1 file changed, 2 deletions(-)
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> How/when is this series being applied?
Pretty soon. Luka mentioned to me off-list, that he planned to apply and
push this series last weekend. Hopefully he will find the time to do it
early this week.
Luka, can you please add this patch to the series as well?
Thanks,
Stefan
prev parent reply other threads:[~2015-05-04 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 15:31 [U-Boot] [PATCH] arm: mvebu: Remove "u-boot.kwb" CONFIG_BUILD_TARGET for non-SPL targets Stefan Roese
2015-05-04 15:35 ` Simon Glass
2015-05-04 15:39 ` Stefan Roese [this message]
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=554792A8.6030501@denx.de \
--to=sr@denx.de \
--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