All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] pulling libfdt testing branch into u-boot-testing?
Date: Fri, 07 Dec 2007 13:05:16 -0500	[thread overview]
Message-ID: <47598B5C.1070504@ge.com> (raw)
In-Reply-To: <AE37FE6C-B1BD-4732-930B-50C7823C3632@kernel.crashing.org>

Kumar Gala wrote:
> Jerry,
> 
> Now that 1.3.1 is out and we are in a merge window can we get the rest 
> of the libfdt testing branch pulled into u-boot-testing?  I need some of 
> that for the 85xx work.
> 
> - k

Hi Kumar,

What patches are hot, or are you looking for issue a pull request for 
stuff that is already in the libfdt tree?  Ahh, I see there are several 
patches in the later category.

I'll work on it... rebase and issue a pull request.

8 days ago
	Kumar Gala
	Convert boards that set memory node to use fdt_fixup ...
	commit | commitdiff | tree | snapshot
8 days ago
	Kumar Gala
	Added fdt_fixup_stdout that uses aliases to set linux,s ...
	commit | commitdiff | tree | snapshot
8 days ago
	Kumar Gala
	Add common memory fixup function
	commit | commitdiff | tree | snapshot
11 days ago
	Kumar Gala
	Conditionally compile fdt_support.c
	commit | commitdiff | tree | snapshot
11 days ago
	Kumar Gala
	Fix build breakage due to libfdt import
	commit | commitdiff | tree | snapshot
13 days ago
	Gerald Van ...
	Add spaces around the = in the fdt print format.
	commit | commitdiff | tree | snapshot

Best regards,
gvb

  reply	other threads:[~2007-12-07 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07 17:48 [U-Boot-Users] pulling libfdt testing branch into u-boot-testing? Kumar Gala
2007-12-07 18:05 ` Jerry Van Baren [this message]
2007-12-07 18:21   ` Kumar Gala
2007-12-26 23:27     ` 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=47598B5C.1070504@ge.com \
    --to=gerald.vanbaren@ge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.