u-boot.git/test, branch next

Merge patch series "boot/fit: use fdt_for_each_subnode() in image-fit.c"

2026-05-25T19:44:28+00:00

Aristo Chen  says:

This series ends with replacing the verbose fdt_next_node() + ndepth
idiom in boot/image-fit.c with fdt_for_each_subnode(), bringing the
file in line with boot/image-fit-sig.c. Six of the seven sites in
image-fit.c predate the macro by 2-6 years; the seventh was
copy-pasted from a neighbour in 2015 just after the macro landed.
The old idiom is legacy, not a deliberate technical choice.

Converting straight to the macro turned out to need a prerequisite,
which is patch 1. fit_print_contents() reads the default-config
property using the loop variable left over after iterating /images
children. With /images defined first in the source (the conventional
layout) libfdt's walker happens to leave that variable pointing at
/configurations and the read works. With /configurations defined
first the read returns NULL and the "Default Configuration" line is
silently omitted. fdt_for_each_subnode()'s post-loop value is
unconditionally a negative error code, so a naive conversion would
have made the missing line the unconditional behaviour. Patch 1
reads the property from confs_noffset directly and removes the
layout dependency.

Patch 2 adds a regression test for the configs-before-images
layout, which had no coverage.

Patch 3 is the mechanical conversion at all seven sites,
equivalence-preserving as described in the per-patch message.

Link: https://lore.kernel.org/r/20260508213217.3807786-1-aristo.chen@canonical.com

test: fit: regression test for default-config print with reversed node order

2026-05-25T19:44:10+00:00

Add a test that builds a FIT whose /configurations node is defined
before /images in the source, runs iminfo, and asserts that the
"Default Configuration: ''" line appears in the output.

Before the fix in the preceding commit ("boot/fit: read default-config
property from the configurations node"), fit_print_contents() read the
default-config property using the loop variable left over from iterating
/images children. With /images defined first that variable accidentally
pointed at /configurations and the line printed correctly; with
/configurations defined first the read returned NULL and the line was
silently omitted. The new test exercises the latter layout, which had
no coverage.

iminfo and the fit_print_contents() path had no test coverage at all
before this commit.

Signed-off-by: Aristo Chen 
Reviewed-by: Simon Glass

test: fs: Use shared generate_file from utils

2026-05-25T19:43:21+00:00

test_fs/test_erofs.py and test_fs/test_squashfs/sqfs_common.py both
defined a generate_file() helper that writes a file of a given size
filled with 'x'. The two functions were functionally identical and
differed only in parameter names and docstrings.

Move the helper into the existing test/py/utils.py module, which is
the established home for generic test utilities (md5sum_file,
PersistentRandomFile, attempt_to_open_file). Update both call sites
to use it.

Signed-off-by: Aristo Chen 
Reviewed-by: joaomarcos.costa@bootlin.com
Reviewed-by: Simon Glass

Merge tag 'v2026.07-rc3' into next

2026-05-25T17:35:35+00:00

Prepare v2026.07-rc3

Merge patch series "add memdup_nul(), use it and memdup() in a few places"

2026-05-12T21:41:52+00:00

Rasmus Villemoes  says:

There are quite a few places where we allocate X+1 bytes, initialize
the first X bytes via memcpy() and then set the last byte to 0.

The kernel has a helper for that, kmemdup_nul(). Introduce a similar
one, and start making use of it in a few places. Also the existing
memdup() helper can be put to more use.

There are lots more places one could modify. But for code shared with
host tools, one would need to do some refactoring, putting memdup()
and memdup_nul() in their own str-util.c TU which could then also be
included in the tools build.

Link: https://lore.kernel.org/r/20260421075439.16696-1-ravi@prevas.dk

test: lib: add test of memdup_nul()

2026-05-12T21:38:00+00:00

Add a very basic test of the new memdup_nul() helper.

Signed-off-by: Rasmus Villemoes 
Reviewed-by: Simon Glass

test: dm: fwu_mdata: add test for fwu_mdata_get_image_guid

2026-05-12T13:52:01+00:00

Add a new unit test for the fwu_mdata_get_image_guid() function.

Signed-off-by: Dario Binacchi 
Reviewed-by: Simon Glass

test: cmd: part: add UUID lookup tests

2026-05-12T13:52:01+00:00

Extend the 'part' command unit tests to include partition lookup via
UUID.

This ensures that the 'number', 'start', and 'size' subcommands
consistently handle UUIDs as partition identifiers, maintaining
parity with the name-based lookup functionality.

Signed-off-by: Dario Binacchi 
Reviewed-by: Simon Glass

test: cmd: add unit tests for part command

2026-05-12T13:52:01+00:00

Add unit tests for the 'part' command, specifically for the 'number',
'start', and 'size' subcommands.

These tests establish a baseline for the current partition lookup
functionality by name. This foundation will be used by subsequent
patches to extend the command, ensuring consistent behavior as new
features are introduced.

Signed-off-by: Dario Binacchi 
Reviewed-by: Simon Glass

test: dm: part: add test for part_get_info_by_uuid

2026-05-12T13:52:01+00:00

Add a new unit test for the part_get_info_by_uuid() function.

Signed-off-by: Dario Binacchi 
Reviewed-by: Simon Glass