All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] "Quality" of patches / testing.
Date: Tue, 18 Oct 2011 19:44:12 +0200	[thread overview]
Message-ID: <4E9DBAEC.5000402@aribaud.net> (raw)
In-Reply-To: <CAF6FioUF9ks=SBRovVkQ3GNzeOER9GG0FOXdAPKmrTtw228y7w@mail.gmail.com>

Le 18/10/2011 19:16, Anton Staaf a ?crit :

> I would like to start a thread addressing this question.  I don't think
> the people submitting are running MAKEALL because it has a very high
> barrier to entry.  In particular I spent a few days trying to get as
> many architecture toolchains up and running as I could so that I could
> run MAKEALL to fully test my builds.  The result was frustrating.  I
> was only able to get ARM to build (Our local toolchain works, but I also
> got the ELDK toolchain to work for me).  I was not able to get the ELDK
> toolchain for PowerPC to work however.
>
> -Anton
>
> Ahh, looks like Mike agrees...

As far as I am concerned, I do run ./MAKEALL arm (or a subset) usually 
before requesting pulls and before applying pull requests, and I have 
ELD and CS ARM toolchains in place, but I never run MAKEALL on other 
arches than ARM.

Amicalement,
-- 
Albert.

  reply	other threads:[~2011-10-18 17:44 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18  6:23 [U-Boot] [STATUS] "Quality" of patches / testing Wolfgang Denk
2011-10-18  6:51 ` Simon Schwarz
2011-10-18  9:22   ` Andreas Bießmann
2011-10-18  9:44     ` Wolfgang Denk
2011-10-18 13:05       ` Jason
2011-10-18 13:10         ` Jason
2011-10-18 13:13         ` Simon Schwarz
2011-10-18 13:49           ` Jason
2011-10-18 15:37             ` Jason
2011-10-18 16:12           ` Mike Frysinger
2011-10-18 13:36         ` Andreas Bießmann
2011-10-18 15:55           ` Jason
2011-10-18 14:05       ` Simon Glass
2011-10-18 16:59         ` Anton Staaf
2011-10-18 20:23         ` Wolfgang Denk
2011-10-20  0:39           ` Simon Glass
2011-10-20 15:32             ` Wolfgang Denk
2011-10-18 10:24     ` Lukasz Majewski
2011-10-18 11:02       ` Wolfgang Denk
2011-10-18  9:34   ` Wolfgang Denk
2011-10-18 13:05     ` Simon Schwarz
2011-10-18  8:49 ` Lukasz Majewski
2011-10-18 17:01 ` [U-Boot] MAKEALL Mike Frysinger
2011-10-18 17:39   ` Simon Glass
2011-10-18 17:58   ` Tom Rini
2011-10-18 18:11     ` Mike Frysinger
2011-10-18 18:31     ` Mike Frysinger
2011-10-18 18:54       ` Tom Rini
2011-10-18 19:49         ` Mike Frysinger
2011-10-18 20:07   ` Wolfgang Denk
2011-10-18 20:14     ` Mike Frysinger
2011-10-18 20:47       ` Wolfgang Denk
2011-10-18 20:55         ` Mike Frysinger
2011-10-18 21:30           ` Simon Glass
2011-10-18 22:21             ` Mike Frysinger
2011-10-19 11:36               ` Albert ARIBAUD
2011-10-19 14:25                 ` Mike Frysinger
2011-10-19 19:57                   ` Wolfgang Denk
2011-10-18 21:50           ` Wolfgang Denk
2011-10-18 22:18             ` Mike Frysinger
2011-10-18 22:33     ` Graeme Russ
2011-10-19  7:12       ` Andreas Bießmann
2011-10-19  8:57       ` Wolfgang Denk
2011-10-18 17:16 ` [U-Boot] [STATUS] "Quality" of patches / testing Anton Staaf
2011-10-18 17:44   ` Albert ARIBAUD [this message]
2011-10-18 18:07     ` Anton Staaf
2011-10-20  9:25 ` Detlev Zundel

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=4E9DBAEC.5000402@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 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.