All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Build errors in u-boot mainline and daily builds
Date: Sat, 3 Jan 2009 06:36:07 -0500	[thread overview]
Message-ID: <200901030636.09893.vapier@gentoo.org> (raw)
In-Reply-To: <3efb10970901030310r7cfc1245g97ac0db4375ddc33@mail.gmail.com>

On Saturday 03 January 2009 06:10:24 Remy Bohmer wrote:
> Currently I only build for ARM based boards, but there is no limit on
> architectures, if I have all the cross-compilers.

the Blackfin tree is already compile tested daily, so i wouldnt waste cycles 
on doing those ... failures get published to the Blackfin u-boot development 
list.

> Further, is there any interest to make the daily build results public?
> * Is it appreciated if I post the build results in a daily post to the
> mailinglist, _if_ there is a build failure? (No news is good news)
> What format is preferred?
> * Or is it preferred to post the results on a website?
> * Or ...

having them public is good, but i'd find posting them to the normal u-boot 
mailing list annoying ... perhaps we should start up another u-boot mailing 
list just to publish these kind of results ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090103/a3514589/attachment.pgp 

  reply	other threads:[~2009-01-03 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 11:10 [U-Boot] [RFC] Build errors in u-boot mainline and daily builds Remy Bohmer
2009-01-03 11:36 ` Mike Frysinger [this message]
2009-01-03 15:18 ` Wolfgang Denk
2009-01-03 17:28   ` Jerry Van Baren
2009-01-03 20:05     ` Remy Bohmer
2009-01-03 20:22       ` Wolfgang Denk
2009-01-03 20:08     ` Wolfgang Denk
2009-01-03 15:37 ` Jean-Christophe PLAGNIOL-VILLARD

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=200901030636.09893.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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.