public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot mainline build fails on MMC
Date: Thu, 19 Feb 2009 21:04:02 +0100	[thread overview]
Message-ID: <20090219200402.D7EB1832E43F@gemini.denx.de> (raw)
In-Reply-To: <3efb10970902190815v2fc3010dg5574891a9ab26f07@mail.gmail.com>

Dear Remy,

In message <3efb10970902190815v2fc3010dg5574891a9ab26f07@mail.gmail.com> you wrote:
> 
> >> I know you do not want build failure messages on the list, but this
> > You are absolutely right - instead of build failure messages I prefer
> > to see patches that fix build failures :-)
> 
> Instead of sending patches, I would prefer such patches not hitting
> mainline at all...

You are right, that would be best.

Next best is to provide fixes.

> I think it is the job of the one who breaks things to repair the
> damage, but that person sometimes needs to be told that he broke
> something, because I assume it is not broken on purpose. That's why I
> posted this build log. Do not shoot the messenger...

The thing is that patches get posted here for review. People are
supposed to have a look at the patches, and eventually even try these
out. If there have no complaints been posted after a couple of days,
patches will get applied.

Even for a very careful submitter it is usually impossible to compile
all boards on all architectures. Speaking for myself, I don't even
have toolchains installed for BlackFin, AVR32, Leon, MicroBlaze, NIOS
and some other archictures - do you?


So we have to rely on co-operation of as many developers in the
community as posible.


> And if the breakage was small, I would already have made a patch. But
> the breakage is that huge here, that I would suggest to revert those
> patches, until the committer has solved the bugs he introduced.

What if the problem doesn't show up on the boards he can build, but
shows up on the boards you can build?

> (If fixing this takes a long time from now, the tree is no longer
> proper bisect-able, therefore reverting could be wiser.)

So please help out...

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The thing is, as you progress in the Craft,  you'll  learn  there  is
another rule... When you break rules, break 'em good and hard.
                                    - Terry Pratchett, _Wyrd Sisters_

      parent reply	other threads:[~2009-02-19 20:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  8:33 [U-Boot] U-boot mainline build fails on MMC Remy Bohmer
2009-02-19 12:15 ` Wolfgang Denk
2009-02-19 16:03   ` Dirk Behme
2009-02-19 16:14     ` Remy Bohmer
2009-02-19 16:24       ` Dirk Behme
2009-02-19 20:12     ` Wolfgang Denk
2009-02-19 16:15   ` Remy Bohmer
2009-02-19 16:42     ` Dirk Behme
2009-02-19 16:57       ` Remy Bohmer
2009-02-19 20:04     ` Wolfgang Denk [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=20090219200402.D7EB1832E43F@gemini.denx.de \
    --to=wd@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