All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot mainline build fails on MMC
Date: Thu, 19 Feb 2009 17:42:50 +0100	[thread overview]
Message-ID: <499D8C0A.809@googlemail.com> (raw)
In-Reply-To: <3efb10970902190815v2fc3010dg5574891a9ab26f07@mail.gmail.com>

Remy Bohmer wrote:
> Hello Wolfgang,
> 
>>> 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...
> 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...
> 
> 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.

Just in case somebody is faster than I :

http://pastebin.com/m43f9d61

fixes OMAP3 build. As mentioned, I will try to send a proper OMAP3 
patch, soon.

I don't know which other boards might be affected, too, and need 
similar changes.

Best regards

Dirk

  reply	other threads:[~2009-02-19 16:42 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 [this message]
2009-02-19 16:57       ` Remy Bohmer
2009-02-19 20:04     ` Wolfgang Denk

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=499D8C0A.809@googlemail.com \
    --to=dirk.behme@googlemail.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 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.