From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10521] New: U-Boot 2017.09 has a bug in fdt set command
Date: Wed, 22 Nov 2017 02:58:51 +0000 [thread overview]
Message-ID: <bug-10521-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=10521
Bug ID: 10521
Summary: U-Boot 2017.09 has a bug in fdt set command
Product: buildroot
Version: 2017.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Outdated package
Assignee: unassigned at buildroot.uclibc.org
Reporter: sjr_ee at yahoo.ca
CC: buildroot at uclibc.org
Target Milestone: ---
There is a bug in U-Boot 2017.09 in the fdt set command, which prevents it from
being able to add a property to a device tree node. That version is the default
in buildroot-2017.11-rc2. U-Boot 2017.11 is now the current release. I haven't
yet confirmed if the bug is fixed in 2017.11.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-11-22 2:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 2:58 bugzilla at busybox.net [this message]
2017-11-23 2:15 ` [Buildroot] [Bug 10521] U-Boot 2017.09 has a bug in fdt set command bugzilla at busybox.net
2018-01-10 20:58 ` bugzilla at busybox.net
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=bug-10521-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.