public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Imminent u-boot-fdt pull request
Date: Fri, 25 May 2007 13:33:49 -0400	[thread overview]
Message-ID: <46571DFD.7080407@smiths-aerospace.com> (raw)
In-Reply-To: <20070525121339.189729bb.kim.phillips@freescale.com>

Kim Phillips wrote:
> On Fri, 25 May 2007 12:56:13 -0400
> Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com> wrote:

[snip]

> please do not ask Wolfgang to pull patches to files in mpc83xx and
> related directories (cpu.c, board configs, etc.) from your tree; they
> should go through the mpc83xx tree from now on.
> 
> Kim

In retrospect, that was impolite and I apologize for the crossover. :-(

The 83xx changes were necessary to make the bootm using libfdt work (I 
have a 8360 board).  If I don't push the necessary changes through 
u-boot-fdt, u-boot-fdt will be impossible to use until you add the 
necessary changes in the 83xx repo (and possibly vice versa).  In 
addition, Wolfgang would have to coordinate his pulls into the main repo 
or it would break.

The cross coupling is unfortunate, but we have to have one example of a 
CPU/board and libfdt coupled in order to test the libfdt changes.

I would prefer to fix the problems noted (which really are not as bad as 
they look IMHO) to make one CPU+board+libfdt example work and push those 
changes to Wolfgang via the u-boot-fdt repo.  If you are opposed to 
this, I can back out the 83xx changes and push just libfdt stuff to 
Wolfgang and supply you with the set of 83xx patches which you can push 
through your repo, but it will tough for others to use/test since they 
will get only half a picture from each repo.

Best regards,
gvb

  reply	other threads:[~2007-05-25 17:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22  4:06 [U-Boot-Users] Imminent u-boot-fdt pull request Jerry Van Baren
2007-05-25  3:26 ` Kim Phillips
2007-05-25  9:27   ` Wolfgang Grandegger
2007-05-25 15:58     ` Kim Phillips
2007-05-25 16:56       ` Jerry Van Baren
2007-05-25 17:13         ` Kim Phillips
2007-05-25 17:33           ` Jerry Van Baren [this message]
2007-05-25 19:36             ` Kim Phillips
2007-05-25 20:18               ` Jerry Van Baren
2007-05-25 18:05         ` Scott Wood
2007-05-25 18:12           ` [U-Boot-Users] HUSH local variables visibility in u-boot code Leonid
2007-05-25 19:33             ` Wolfgang Denk
2007-05-25 18:15           ` [U-Boot-Users] Imminent u-boot-fdt pull request Jerry Van Baren
2007-05-25 18:17             ` Scott Wood
2007-05-25 18:31               ` Jerry Van Baren
2007-05-25 17:06       ` Jerry Van Baren
2007-05-25 11:54   ` Jerry Van Baren
2007-05-25 15:58     ` Kim Phillips
2007-05-25 16:28       ` Jerry Van Baren

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=46571DFD.7080407@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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