From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] fdt: add support the ePAPR "phandle" property
Date: Fri, 6 May 2011 13:53:22 -0500 [thread overview]
Message-ID: <4DC443A2.4030808@freescale.com> (raw)
In-Reply-To: <BANLkTikKibkiwwJ8B_px4E9DtEJmk3jyjg@mail.gmail.com>
Grant Likely wrote:
> As discussed on IRC, upstream libfdt already supports the "phandle"
> property, so u-boot needs to be updated to the latest version from the
> dtc.git repo on git.jdl.com. You'll still need the change to
> common/fdt_support.c though.
Upstream libfdt was fixed back in 2009. Why is U-Boot and Linux so outdated?
Shouldn't there be a regular plan to update U-boot and Linux as libfdt is
updated? I don't see how an 18-month backlog is acceptable.
No offense, but this sounds like something the U-boot fdt maintainer is supposed
to be doing regularly.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2011-05-06 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 17:56 [U-Boot] [PATCH 1/2] fdt: add support the ePAPR "phandle" property Timur Tabi
2011-05-06 17:56 ` [U-Boot] [PATCH 2/2] powerpc/85xx: " Timur Tabi
2011-05-06 18:46 ` [U-Boot] [PATCH 1/2] fdt: " Grant Likely
2011-05-06 18:53 ` Timur Tabi [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=4DC443A2.4030808@freescale.com \
--to=timur@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox