From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot patch submission process
Date: Mon, 11 Feb 2008 09:26:25 +0100 [thread overview]
Message-ID: <20080211092625.4d09fe0b@siona> (raw)
In-Reply-To: <47AFD266.2060507@googlemail.com>
On Mon, 11 Feb 2008 05:43:18 +0100
Dirk Behme <dirk.behme@googlemail.com> wrote:
> [U-Boot-Users] [PATCH] [DRIVERS] <asm/mpc8xxx_spi.h> is onlyavailable
> for ppc boards.
>
> I'm assuming this will eventually be properly patched in the main tree
> - meanwhile anyone building ARM code can apply this patch
> -- cut --
>
> This is quite annoying, particularly if you should test patches
> already in that tree or against that. IMHO the arm.git should contain
> the fix temporarily to be able to build cleanly instead of staying
> with a broken tree.
You're damn right it's annoying, but applying the fix to every single
arch tree just isn't the right solution. That will cause mayhem when it
turns out that every arch maintainer picked up a different fix among
the 6 or so that were posted.
But if Wolfgang doesn't wake up and apply a fix pretty soon, I guess
that might be exactly what's going to happen.
> To workaround I would propose that you test MAKEALL against mainline
> U-Boot git.
Won't help since it's mainline that is broken. And it's not only ARM --
every single architecture except PPC has been broken for several weeks.
The first fix was posted less than three hours after the breakage was
introduced, but no fix has yet been merged.
I'm starting to get seriously pissed off about this whole situation and
how it's been handled. Wolfgang, you can't with a straight face demand
that people always run the latest git snapshot WHEN IT DOESN'T EVEN
BUILD AND HAS BEEN THAT WAY FOR SEVERAL WEEKS!
Haavard
next prev parent reply other threads:[~2008-02-11 8:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 16:33 [U-Boot-Users] [PATCH] [DRIVERS] <asm/mpc8xxx_spi.h> is only available for ppc boards Peter Pearse
2008-01-24 16:50 ` Andy Fleming
2008-01-24 17:01 ` Kim Phillips
2008-02-08 22:48 ` Ladislav Michl
2008-02-09 0:10 ` Ben Warren
2008-02-09 0:43 ` Ladislav Michl
2008-02-09 2:35 ` Ben Warren
2008-02-11 0:38 ` [U-Boot-Users] u-boot patch submission process Todd Fischer
2008-02-11 4:43 ` Dirk Behme
2008-02-11 8:26 ` Haavard Skinnemoen [this message]
2008-02-11 15:03 ` [U-Boot-Users] Broken (ARM) build, was: " Dirk Behme
2008-02-11 23:25 ` [U-Boot-Users] " Wolfgang Denk
2008-02-12 9:36 ` Peter Pearse
2008-02-12 10:22 ` Haavard Skinnemoen
2008-02-12 22:52 ` Wolfgang Denk
2008-02-13 19:04 ` Jerry Van Baren
2008-02-13 22:55 ` Wolfgang Denk
2008-02-11 9:01 ` Peter Pearse
2008-03-23 0:34 ` [U-Boot-Users] [PATCH] [DRIVERS] <asm/mpc8xxx_spi.h> is only available for ppc boards Wolfgang Denk
2008-03-23 0:46 ` Ben Warren
2008-02-09 0:14 ` Haavard Skinnemoen
2008-01-24 17:28 ` Ben Warren
2008-01-24 18:18 ` [U-Boot-Users] ppc start.S 'rfmci' opcode not recognized by ppc-440 compiler k b
2008-01-24 23:16 ` 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=20080211092625.4d09fe0b@siona \
--to=hskinnemoen@atmel.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