test: boot: Use a consistent name for the script bootmeth

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 <sjg@chromium.org>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>

diff --git a/test/boot/bootflow.c b/test/boot/bootflow.c
index 0d4e966892efdf0ee87f7d4d3e2e29b9b1a753d1..8762d21ef3c3eb0241bbfb0bfcda6b5c138ab9ea 100644 (file)
--- 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) {