[PATCH 1/1] test:dm:fix typo

[Yuepeng Xing]

Fix typos in the 'test/dm' directory.

Signed-off-by: Yuepeng Xing <xingyuepeng at eswincomputing.com>
---
 test/dm/blk.c        | 2 +-
 test/dm/button.c     | 4 ++--
 test/dm/gpio.c       | 4 ++--
 test/dm/host.c       | 2 +-
 test/dm/remoteproc.c | 2 +-
 test/dm/scmi.c       | 2 +-
 test/dm/spmi.c       | 2 +-
 test/dm/test-fdt.c   | 2 +-
 8 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/test/dm/blk.c b/test/dm/blk.c
index 612f3ffb32..0aa04c64ef 100644
--- a/test/dm/blk.c
+++ b/test/dm/blk.c
@@ -127,7 +127,7 @@ static int dm_test_blk_devnum(struct unit_test_state *uts)
 
 	/*
 	 * Probe the devices, with the first one being probed last. This is the
-	 * one with no alias / sequence numnber.
+	 * one with no alias / sequence number.
 	 */
 	ut_assertok(uclass_get_device(UCLASS_MMC, 1, &dev));
 	ut_assertok(uclass_get_device(UCLASS_MMC, 2, &dev));
diff --git a/test/dm/button.c b/test/dm/button.c
index f8a7fab61d..e76c1ad030 100644
--- a/test/dm/button.c
+++ b/test/dm/button.c
@@ -46,7 +46,7 @@ static int dm_test_button_gpio(struct unit_test_state *uts)
 	struct udevice *dev, *gpio;
 
 	/*
-	 * Check that we can manipulate an BUTTON. BUTTON 1 is connected to GPIO
+	 * Check that we can manipulate a BUTTON. BUTTON 1 is connected to GPIO
 	 * bank gpio_a, offset 3.
 	 */
 	ut_assertok(uclass_get_device(UCLASS_BUTTON, 1, &dev));
@@ -64,7 +64,7 @@ static int dm_test_button_gpio(struct unit_test_state *uts)
 }
 DM_TEST(dm_test_button_gpio, UT_TESTF_SCAN_PDATA | UT_TESTF_SCAN_FDT);
 
-/* Test obtaining an BUTTON by label */
+/* Test obtaining a BUTTON by label */
 static int dm_test_button_label(struct unit_test_state *uts)
 {
 	struct udevice *dev, *cmp;
diff --git a/test/dm/gpio.c b/test/dm/gpio.c
index a8c35d4370..0d88ec24bd 100644
--- a/test/dm/gpio.c
+++ b/test/dm/gpio.c
@@ -348,7 +348,7 @@ static int dm_test_gpio_phandles(struct unit_test_state *uts)
 	ut_asserteq(-ENOENT, gpio_request_by_name(dev, "test-gpios", 5, &desc,
 						  0));
 
-	/* Last GPIO is ignord as it comes after <0> */
+	/* Last GPIO is ignored as it comes after <0> */
 	ut_asserteq(3, gpio_request_list_by_name(dev, "test-gpios", desc_list,
 						 ARRAY_SIZE(desc_list), 0));
 	ut_asserteq(-EBUSY, gpio_request_list_by_name(dev, "test-gpios",
@@ -377,7 +377,7 @@ static int dm_test_gpio_phandles(struct unit_test_state *uts)
 	ut_asserteq(6, gpio_request_list_by_name(dev, "test2-gpios", desc_list,
 						 ARRAY_SIZE(desc_list), 0));
 
-	/* This was set to output previously but flags resetted to 0 = INPUT */
+	/* This was set to output previously but flags reset to 0 = INPUT */
 	ut_asserteq(0, sandbox_gpio_get_flags(gpio_a, 1));
 	ut_asserteq(GPIOF_INPUT, gpio_get_function(gpio_a, 1, NULL));
 
diff --git a/test/dm/host.c b/test/dm/host.c
index 4dafc24abb..355ba7770a 100644
--- a/test/dm/host.c
+++ b/test/dm/host.c
@@ -132,7 +132,7 @@ static int dm_test_cmd_host(struct unit_test_state *uts)
 
 	ut_assertok(run_commandf("host bind fat %s", filename2));
 
-	/* Check it is not removeable (no '-r') */
+	/* Check it is not removable (no '-r') */
 	ut_assertok(uclass_next_device_err(&dev));
 	ut_assertok(blk_get_from_parent(dev, &blk));
 	desc = dev_get_uclass_plat(blk);
diff --git a/test/dm/remoteproc.c b/test/dm/remoteproc.c
index 1cc07bc808..915c1f67ca 100644
--- a/test/dm/remoteproc.c
+++ b/test/dm/remoteproc.c
@@ -139,7 +139,7 @@ static int dm_test_remoteproc_elf(struct unit_test_state *uts)
 		0x20, 0x00, 0x00, 0x00,
 		/* memsz = filesz */
 		0x20, 0x00, 0x00, 0x00,
-		/* flags : readable and exectuable */
+		/* flags : readable and executable */
 		0x05, 0x00, 0x00, 0x00,
 		/* padding */
 		0x00, 0x00, 0x00, 0x00,
diff --git a/test/dm/scmi.c b/test/dm/scmi.c
index 795f207304..93c7d08f43 100644
--- a/test/dm/scmi.c
+++ b/test/dm/scmi.c
@@ -6,7 +6,7 @@
  * uclass devices probe when a SCMI server exposes resources.
  *
  * Note in test.dts the protocol at 10 node in scmi node. Protocol 0x10 is not
- * implemented in U-Boot SCMI components but the implementation is exepected
+ * implemented in U-Boot SCMI components but the implementation is expected
  * to not complain on unknown protocol IDs, as long as it is not used. Note
  * in test.dts tests that SCMI drivers probing does not fail for such an
  * unknown SCMI protocol ID.
diff --git a/test/dm/spmi.c b/test/dm/spmi.c
index 114fd2d22e..9cc284b98c 100644
--- a/test/dm/spmi.c
+++ b/test/dm/spmi.c
@@ -17,7 +17,7 @@
 #include <test/test.h>
 #include <test/ut.h>
 
-/* Test if bus childs got probed propperly*/
+/* Test if bus children got probed properly*/
 static int dm_test_spmi_probe(struct unit_test_state *uts)
 {
 	const char *name = "spmi at 0";
diff --git a/test/dm/test-fdt.c b/test/dm/test-fdt.c
index 8bb868b678..7cd2d04612 100644
--- a/test/dm/test-fdt.c
+++ b/test/dm/test-fdt.c
@@ -592,7 +592,7 @@ static int dm_test_fdt_translation(struct unit_test_state *uts)
 	ut_asserteq_str("dev at 2,200", dev->name);
 	ut_asserteq(0xA000, dev_read_addr(dev));
 
-	/* No translation for busses with #size-cells == 0 */
+	/* No translation for buses with #size-cells == 0 */
 	ut_assertok(uclass_find_device_by_seq(UCLASS_TEST_DUMMY, 3, &dev));
 	ut_asserteq_str("dev at 42", dev->name);
 	ut_asserteq(0x42, dev_read_addr(dev));
-- 
2.31.1.windows.1