From: David Gibson <david@gibson.dropbear.id.au>
To: linuxppc-dev@ozlabs.org
Subject: Re: libfdt - flat tree manipulation library
Date: Wed, 29 Nov 2006 16:59:04 +1100 [thread overview]
Message-ID: <20061129055904.GA11883@localhost.localdomain> (raw)
In-Reply-To: <20061127055905.GA6428@localhost.localdomain>
On Mon, Nov 27, 2006 at 04:59:05PM +1100, David Gibson wrote:
[snip]
> The code, such as it is, is at:
> git://ozlabs.org/home/dgibson/git/libfdt.git
Code for writing device trees from scratch, sequentially, is now
implemented.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2006-11-29 5:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 5:59 libfdt - flat tree manipulation library David Gibson
2006-11-29 5:59 ` David Gibson [this message]
2006-12-01 6:00 ` David Gibson
2006-12-01 13:11 ` Jerry Van Baren
2006-12-03 23:55 ` David Gibson
2006-12-02 8:41 ` Grant Likely
2006-12-04 0:03 ` David Gibson
2006-12-07 20:35 ` Hollis Blanchard
2006-12-07 22:23 ` David Gibson
2007-01-02 23:29 ` Mark A. Greer
2007-01-03 1:32 ` David Gibson
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=20061129055904.GA11883@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).