From: Jon Loeliger <jdl@jdl.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] DTC 1.2.0-rc1 Tagged
Date: Thu, 19 Jun 2008 11:58:05 -0500 [thread overview]
Message-ID: <E1K9NSX-0004BS-95@jdl.com> (raw)
Folks,
I've pushed out a freshly tagged DTC 1.2.0-rc1 to jdl.com.
Please feel free to test it!
Thanks,
jdl
David Gibson (34):
libfdt: Add and use a node iteration helper function.
libfdt: Fix NOP handling bug in fdt_add_subnode_namelen()
dtc: Fold comment handling test into testsuite
libfdt: More tests of NOP handling behaviour
libfdt: Trivial cleanup for CHECK_HEADER)
libfdt: Remove no longer used code from fdt_node_offset_by_compatible()
dtc: Fix error reporting in push_input_file()
dtc: Implement checks for the format of node and property names
dtc: Fix indentation of fixup_phandle_references
dtc: Strip redundant "name" properties
dtc: Test and fix conversion to/from old dtb versions
dtc: Use for_each_marker_of_type in asm_emit_data()
dtc: Make -I dtb mode use fill_fullpaths()
dtc: Make eval_literal() static
dtc: Assorted improvements to test harness
dtc: Testcases for input handling
dtc: Make dtc_open_file() die() if unable to open requested file
dtc: Remove ugly include stack abuse
dtc: Abolish asize field of struct data
dtc: Add some documentation for the dts formta
dtc: Cleanup \nnn and \xNN string escape handling
dtc: Change exit code for usage message
dtc: Simplify error handling for unparseable input
dtc: Clean up included Makefile fragments
dtc: Trivial formatting fixes
dtc: Make dt_from_blob() open its own input file, like the other input formats
dtc: Rework handling of boot_cpuid_phys
dtc: Add program to convert dts files from v0 to v1
dtc: Remove reference to dead Makefile variables
libfdt: Several cleanups to parameter checking
dtc: Remove some small bashisms from test scripts
dtc: Fix some printf() format warnings when compiling 64-bit
dtc: Add a testcase for 'reg' or 'ranges' in /
dtc: Add support for binary includes.
Jon Loeliger (1):
Tag Version 1.2.0-rc1
reply other threads:[~2008-06-19 16:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1K9NSX-0004BS-95@jdl.com \
--to=jdl@jdl.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