public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Boards compiled twice in ./MAKEALL arm?
Date: Sat, 05 Nov 2011 13:06:45 +0100	[thread overview]
Message-ID: <4EB526D5.2080607@aribaud.net> (raw)

Hi all,

When applying the meesc mach-type patch, I noticed a weird thing: on 
commit 867b96a5b7b1de56181b57bdfb25151c01a0fb3f, just before fixing 
meesc, I did a ./MAKEALL arm and noticed that some boards were mentioned 
twice in the build summary:

--------------------- SUMMARY ----------------------------
Boards compiled: 255
Boards with warnings or errors: 67 ( a320evb eb_cpux9k2 VCMA9 
sbc35_a9g20_nandflash sbc35_a9g20_eeprom tny_a9g20_nandflash 
tny_a9g20_eeprom tny_a9260_nandflash tny_a9260_eeprom meesc 
meesc_dataflash otc570 otc570_dataflash pm9261 pm9263 pm9g45 da830evm 
da850evm cam_enc_4xx hawkboard_nand davinci_schmoogie davinci_sonata 
km_kirkwood km_kirkwood_pci mgcoge3un portl2 jadecpu dkb tt01 
mx31pdk_nand smdk6400 ca9x4_ct_vxp am335x_evm omap3_mvblx omap4_panda 
harmony seaboard eb_cpux9k2 sbc35_a9g20_nandflash sbc35_a9g20_eeprom 
tny_a9g20_nandflash tny_a9g20_eeprom tny_a9260_nandflash 
tny_a9260_eeprom meesc meesc_dataflash otc570 otc570_dataflash pm9261 
pm9263 pm9g45 cerf250 cradle csb226 innokom pleb2 xm250 actux1_4_16 
actux1_8_16 actux1_4_32 actux1_8_32 actux2 actux3 actux4 dvlhost pdnb3 
scpu )
----------------------------------------------------------

Namely, the wole of 'sbc35_a9g20_nandflash sbc35_a9g20_eeprom 
tny_a9g20_nandflash tny_a9g20_eeprom tny_a9260_nandflash 
tny_a9260_eeprom meesc meesc_dataflash otc570 otc570_dataflash pm9261 
pm9263 pm9g45' is mentioned twice.

Anyone have any idea why?

Amicalement,
-- 
Albert.

                 reply	other threads:[~2011-11-05 12:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4EB526D5.2080607@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --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