From: Tabi Timur-B04825 <B04825-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: Device Tree Mailing List
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Next formal dtc release?
Date: Mon, 9 May 2011 20:32:05 +0000 [thread overview]
Message-ID: <BANLkTinj4ZKoCwk0eRbg6RaPu5XYzzaqDg@mail.gmail.com> (raw)
In-Reply-To: <E1QJAKI-0007c1-RV-CYoMK+44s/E@public.gmane.org>
On Sun, May 8, 2011 at 3:11 PM, Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org> wrote:
> I have signed and pushed out a tagged Version 1.3.0 release
> of the Device Tree Compiler. Find it at git.jdl.com.
Thanks, Jon.
Can someone update libfdt in the U-Boot, please? I need support for
the ePAPR-compliant "phandle" property.
I don't know what the process is for getting libfdt officially updated
in U-boot.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2011-05-09 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 1:26 Next formal dtc release? David VomLehn
[not found] ` <20110420012610.GA6895-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>
2011-04-20 2:37 ` Grant Likely
[not found] ` <BANLkTi=JxBUEUGq_b+8w5c+LYq9-dKV+Bw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-04-20 3:19 ` Jon Loeliger
[not found] ` <E1QCNwx-0003YA-Pv-CYoMK+44s/E@public.gmane.org>
2011-04-20 22:14 ` David VomLehn
[not found] ` <20110420221426.GA18409-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>
2011-04-21 1:41 ` David Gibson
2011-05-05 6:55 ` Robert Schwebel
[not found] ` <20110505065559.GX3811-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-05-06 13:46 ` Jon Loeliger
[not found] ` <E1QILMd-0008Db-VP-CYoMK+44s/E@public.gmane.org>
2011-05-08 20:11 ` Jon Loeliger
[not found] ` <E1QJAKI-0007c1-RV-CYoMK+44s/E@public.gmane.org>
2011-05-09 8:23 ` Robert Schwebel
2011-05-09 20:32 ` Tabi Timur-B04825 [this message]
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=BANLkTinj4ZKoCwk0eRbg6RaPu5XYzzaqDg@mail.gmail.com \
--to=b04825-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=jdl-CYoMK+44s/E@public.gmane.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).