public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Pull request: u-boot-fdt
Date: Wed, 11 Jun 2008 22:40:22 +0200	[thread overview]
Message-ID: <20080611204022.64FD424345@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 10 Jun 2008 23:05:33 EDT." <20080611030533.GA26116@cideas.com>

In message <20080611030533.GA26116@cideas.com> you wrote:
> Dear Wolfgang,
> 
> I've added Kim's and my working_fdt improvements to my previous pull requests.
> 
> Thanks,
> gvb
> 
> The following changes since commit 8155efbd7ae9c65564ca98affe94631d612ae088:
>   Wolfgang Denk (1):
>         Merge branch 'master' of ssh://mercury/home/wd/git/u-boot/master
> 
> are available in the git repository at:
> 
>   git://git.denx.de/u-boot-fdt.git master
> 
> David Gibson (1):
>       libfdt: Several cleanups to parameter checking
> 
> Gerald Van Baren (6):
>       Convert mpc7448hpc2 to CONFIG_OF_LIBFDT
>       Change the stxxst to CONFIG_OF_LIBFDT
>       Remove the deprecated CONFIG_OF_FLAT_TREE
>       The fdt boardsetup command criteria was not unique
>       Use strncmp() for the fdt command
>       libfdt: Move the working_fdt pointer to cmd_fdt.c
> 
> Kim Phillips (1):
>       fdt: unshadow global working fdt variable
> 
>  README                                    |    9 +-
>  board/freescale/mpc7448hpc2/mpc7448hpc2.c |   21 +-
>  board/tqm8272/tqm8272.c                   |    4 -
>  common/Makefile                           |    1 -
>  common/cmd_fdt.c                          |  134 +++++----
>  common/fdt_support.c                      |    5 -
>  common/ft_build.c                         |  471 -----------------------------
>  cpu/74xx_7xx/cpu.c                        |   35 +--
>  drivers/pci/tsi108_pci.c                  |   33 ++-
>  include/configs/mpc7448hpc2.h             |    3 +-
>  include/configs/stxxtc.h                  |    4 +-
>  include/ft_build.h                        |   71 -----
>  include/libfdt_env.h                      |    2 +-
>  lib_ppc/bootm.c                           |    2 +-
>  libfdt/fdt.c                              |   17 +-
>  libfdt/fdt_ro.c                           |   26 +--
>  libfdt/fdt_rw.c                           |   24 +-
>  libfdt/fdt_sw.c                           |   31 +-
>  libfdt/libfdt_internal.h                  |    1 +
>  19 files changed, 161 insertions(+), 733 deletions(-)
>  delete mode 100644 common/ft_build.c
>  delete mode 100644 include/ft_build.h

Applied. Thanks.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
So we follow our wandering paths, and the very darkness acts  as  our
guide and our doubts serve to reassure us. - Jean-Pierre de Caussade,
eighteenth-century Jesuit priest

  reply	other threads:[~2008-06-11 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-11  3:05 [U-Boot-Users] Pull request: u-boot-fdt Jerry Van Baren
2008-06-11 20:40 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-09 11:58 Jerry Van Baren
2008-06-09 12:07 ` Jerry Van Baren
2007-08-17 10:54 Jerry Van Baren
2007-08-18 19:45 ` 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=20080611204022.64FD424345@gemini.denx.de \
    --to=wd@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