From: Roland Hieber <rhi@pengutronix.de>
To: oss-tools@pengutronix.de
Subject: [OSS-Tools] [dt-utils] Release 2023.11.0
Date: Fri, 24 Nov 2023 12:04:21 +0100 [thread overview]
Message-ID: <20231124110421.ls7jczotswogxg5d@pengutronix.de> (raw)
Hi,
I've just release dt-utils version 2023.11.0. You can download it at the
usual location:
https://public.pengutronix.de/software/dt-utils/dt-utils-2023.08.0.tar.xz
The file checksums are as follows:
* MD5: 4aa4ef310c76a2baa5df62254f0b7453
* SHA1: 3d9556c78c3894ef13fbf9b58eb66d1c11950563
* SHA256: d224d941c076c143f43d59cd7c6e1c522926064a31ac34a67720632ddecb6b53
A small bugfix release, mainly consisting of the following commit:
* commit b67e96895f52 "libdt: prefer first found disk when looking for
block devices"
When using barebox-state on boards with a barbeox-state partition on
an eMMC device, it could happen that barebox-state tried to find a GPT
partition on /dev/mmcblkXbootN instead of /dev/mmcblkX, obviously
failing to find a matching partition there, and quitting without any
further action. This commit restores the old behaviour of using the
first found MMC device (/dev/mmcblkX) instead of the last one.
Although this is not completely future-proof, it has worked for years
and serves a good stop-gap solution for now.
A few more housekeeping and maintenance commits:
* commit feca1c1ffdaa "README: provide git format.subjectPrefix line to copy"
* commit 1cd62596dbd7 "meson: align libdt-utils version with autotools'"
This release includes contributions by Ahmad Fatoum, Enrico Jörns, Leonard
Göhrs, and Roland Hieber. Thank you to all contributors!
--
Roland Hieber, Pengutronix e.K. | r.hieber@pengutronix.de |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next reply other threads:[~2023-11-24 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 11:04 Roland Hieber [this message]
2023-11-24 12:09 ` Ahmad Fatoum
2023-11-27 18:10 ` Roland Hieber
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=20231124110421.ls7jczotswogxg5d@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=oss-tools@pengutronix.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