public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please apply [PATCH V2] ARM: Update mach-types
Date: Wed, 19 Oct 2011 03:06:59 +0200	[thread overview]
Message-ID: <201110190306.59348.marek.vasut@gmail.com> (raw)
In-Reply-To: <4E9E1B5D.9090506@aribaud.net>

On Wednesday, October 19, 2011 02:35:41 AM Albert ARIBAUD wrote:
> Le 18/10/2011 22:13, Albert ARIBAUD a ?crit :
> > Hi Marek,
> > 
> > Le 05/10/2011 13:03, Marek Vasut a ?crit :
> >> Hi guys,
> >> 
> >> my KMail seems to have some bugs, which I need to investigate. Albert,
> >> can you please apply "[PATCH V2] ARM: Update mach-types" ? It was
> >> submitted to ML on Sept. 13.
> >> 
> >> Thanks
> > 
> > Currently running MAKEALL arm in order to find out which boards are
> > affected.
> > 
> > Amicalement,
> 
> MAKELL before patch:
> 
> --------------------- SUMMARY ----------------------------
> Boards compiled: 247
> Boards with warnings or errors: 19 ( km_kirkwood km_kirkwood_pci
> mgcoge3un portl2 smdk6400 ca9x4_ct_vxp devkit8000 omap4_panda
> omap4_sdp4430 actux1_4_16 actux1_8_16 actux1_4_32 actux1_8_32 actux2
> actux3 actux4 dvlhost pdnb3 scpu )
> ----------------------------------------------------------
> 
> (half the failing boards are actually BE boards that the LE ELDK42
> cannot build)
> 
> After patch;
> 
> --------------------- SUMMARY ----------------------------
> Boards compiled: 247
> Boards with warnings or errors: 62 ( a320evb eb_cpux9k2 VCMA9 gplugd
> 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
> davinci_schmoogie davinci_sonata km_kirkwood km_kirkwood_pci mgcoge3un
> portl2 jadecpu tx25 smdk6400 ca9x4_ct_vxp vision2 dig297 devkit8000
> omap4_panda omap4_sdp4430 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 )
> ----------------------------------------------------------
> 
> Sampling some boards: a320evb, pm9261, csb226 confirms the new failures
> are due to missing machine defs.
> 
> So there are 62-19=43 boards affected by this patch -- which is a lot...
> 
> I shall send out an e-mail to the board maintainers of affected boards,
> letting them know that a patch to fix their board is needed before the
> december release.
> 
> Amicalement,

Hi Albert,

please also amend that if the board will not be fixed, it will be removed.

Next time I do such patch, I'll be sending such letters myself.

Cheers

  reply	other threads:[~2011-10-19  1:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 11:03 [U-Boot] Please apply [PATCH V2] ARM: Update mach-types Marek Vasut
2011-10-18 20:13 ` Albert ARIBAUD
2011-10-19  0:35   ` Albert ARIBAUD
2011-10-19  1:06     ` Marek Vasut [this message]
2011-10-19  6:09       ` 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=201110190306.59348.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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