From: Scott Wood <scottwood@freescale.com>
To: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 05/18] Add ft_first_node().
Date: Wed, 24 Jan 2007 15:59:18 -0600 [thread overview]
Message-ID: <45B7D6B6.2010308@freescale.com> (raw)
In-Reply-To: <45B7D044.7020007@smiths-aerospace.com>
Jerry Van Baren wrote:
> Have you considered replacing flatdevtree.c with David Gibson's fdtlib?
> The interface is a lot cleaner, which likely carries through to the
> underlying code.
> <http://thread.gmane.org/gmane.linux.ports.ppc64.devel/12771/focus=12877>
I tried pulling from the git tree, but since I'm using the http protocol
(our firewall unfortunately won't allow the git protocol to go through),
all I get is:
Cannot get remote repository information.
Perhaps git-update-server-info needs to be run there?
-Scott
next prev parent reply other threads:[~2007-01-24 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 21:07 [PATCH 05/18] Add ft_first_node() Scott Wood
2007-01-24 21:31 ` Jerry Van Baren
2007-01-24 21:59 ` Scott Wood [this message]
2007-01-24 23:37 ` David Gibson
2007-01-24 21:46 ` Segher Boessenkool
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=45B7D6B6.2010308@freescale.com \
--to=scottwood@freescale.com \
--cc=gerald.vanbaren@smiths-aerospace.com \
--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).