public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH, 4th resend] Support uImage files for the AVR32 architecture
Date: Fri, 22 Sep 2006 19:09:35 +0200	[thread overview]
Message-ID: <200609221909.36848.sr@denx.de> (raw)
In-Reply-To: <20060922140952.1f5c7fa1@cad-250-152.norway.atmel.com>

Hi Haavard,

On Friday 22 September 2006 14:09, Haavard Skinnemoen wrote:
> I've already sent this patch three times to the list, and I have still
> not gotten any response. It is really important for us to know if you
> intend to merge this or not; until then, there is no point for us to
> change the architecture ID as there will still be a possibility that
> someone else comes along and takes it.

Yes, we intend to merge you patches, but I can't tell you right now if they 
will be accepted as is or if additional changes are required. Wolfgang is on 
vacation and hopefully we will find the time in the not too far future to 
catch up with the pending patches.

> Keeping the current AVR32 architecture ID will mean that our version of
> busybox will be incompatible with the upstream version because it
> clashes with the Blackfin ID. And the longer it takes before we get an
> "official" ID, the harder it will be for us to change it.

Is there already an AVR32 architecture ID? I can't see one. It seems you are 
creating the new ID #17, right? How does it "clash" with the Blackfin ID?

> So if we don't get this issue resolved soon, I see no point in trying
> to contribute our changes back to you at all. This would be very
> unfortunate and effectively create an incompatible fork of u-boot with
> small chances of ever merging in the future.

It could only be a problem, if another architecture ID patch is in our U-Boot 
patch queue, _before_ your patch is incorporated. I don't have an overview 
right now, but find it very unlikely.

Sorry for the inconvenience. Please be assured that we really what to change 
this pending patches dilemma we are in right now.

Best regards,
Stefan

  reply	other threads:[~2006-09-22 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-22 12:09 [U-Boot-Users] [PATCH, 4th resend] Support uImage files for the AVR32 architecture Haavard Skinnemoen
2006-09-22 17:09 ` Stefan Roese [this message]
2006-09-22 17:31   ` Ulf Samuelsson
2006-09-22 17:34   ` Haavard Skinnemoen
2006-10-09  8:09     ` Haavard Skinnemoen
2006-10-09 12:54 ` Stefan Roese
2006-10-09 14:55   ` Haavard Skinnemoen
2006-10-09 15:00     ` Stefan Roese

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=200609221909.36848.sr@denx.de \
    --to=sr@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