Hi Simon, Thank you for the patch.
On sam., oct. 19, 2024 at 09:21, Simon Glass <[email protected]> wrote: > In the bootflow tests the script bootmeth is bound with the name > bootmeth_script whereas the others have a name without the bootmeth_ > prefix. Adjust it to be the same. > > Signed-off-by: Simon Glass <[email protected]> Reviewed-by: Mattijs Korpershoek <[email protected]> > --- > > (no changes since v1) > > test/boot/bootflow.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/test/boot/bootflow.c b/test/boot/bootflow.c > index 154dea70a59..8ea284098e7 100644 > --- a/test/boot/bootflow.c > +++ b/test/boot/bootflow.c > @@ -542,7 +542,7 @@ static int prep_mmc_bootdev(struct unit_test_state *uts, > const char *mmc_dev, > /* Enable the script bootmeth too */ > ut_assertok(uclass_first_device_err(UCLASS_BOOTSTD, &bootstd)); > ut_assertok(device_bind(bootstd, DM_DRIVER_REF(bootmeth_2script), > - "bootmeth_script", 0, ofnode_null(), &dev)); > + "script", 0, ofnode_null(), &dev)); > > /* Enable the cros bootmeth if needed */ > if (IS_ENABLED(CONFIG_BOOTMETH_CROS) && bind_cros_android) { > -- > 2.34.1
