public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: gvb.uboot <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Pull request: u-boot-fdt testing branch for u-boot-testing repo
Date: Fri, 07 Dec 2007 23:08:11 -0500	[thread overview]
Message-ID: <475A18AB.7020306@gmail.com> (raw)

Dear Wolfgang,

Please pull from the testing branch at
   git://denx.de/git/u-boot-fdt.git testing
into your u-boot-testing repo.

I'm all confused over pulling from branches.  If it is more convenient, 
I can move the changes to the "master" branch and re-issue the pull request.

Thanks,
gvb

The following changes since commit 41be969f4957115ed7b1fe8b890bfaee99d7a7a2:
   Wolfgang Denk (1):
         Release v1.3.1

are available in the git repository at:

   git://www.denx.de/git/u-boot-fdt.git testing

Gerald Van Baren (2):
       Add spaces around the = in the fdt print format.
       Conditionally compile fdt_fixup_ethernet()

Kumar Gala (5):
       Fix build breakage due to libfdt import
       Conditionally compile fdt_support.c
       Add common memory fixup function
       Added fdt_fixup_stdout that uses aliases to set linux,stdout-path
       Convert boards that set memory node to use fdt_fixup_memory()

  board/cm5200/cm5200.c   |   15 +-----
  board/ids8247/ids8247.c |   17 +-----
  common/Makefile         |    3 +-
  common/cmd_fdt.c        |    4 +-
  common/fdt_support.c    |  130 
+++++++++++++++++++++++++++++++++++++++++++++--
  cpu/mpc83xx/cpu.c       |   18 +------
  include/fdt_support.h   |    1 +
  7 files changed, 136 insertions(+), 52 deletions(-)

             reply	other threads:[~2007-12-08  4:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08  4:08 gvb.uboot [this message]
2007-12-26 23:27 ` [U-Boot-Users] Pull request: u-boot-fdt testing branch for u-boot-testing repo 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=475A18AB.7020306@gmail.com \
    --to=gvb.uboot@gmail.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