[PATCH] doc: Replace dm_dump_all() with dm_dump_tree()

[PATCH] doc: Replace dm_dump_all() with dm_dump_tree()

[Dylan Corrales]

Replace dm_dump_all() with dm_dump_tree() in driver model documentation,
to reflect changes introduced in commit 145287040480 ("dm: core: Rename
dm_dump_all()").

Signed-off-by: Dylan Corrales <deathcamel58@gmail.com>
---

 doc/develop/driver-model/debugging.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/develop/driver-model/debugging.rst b/doc/develop/driver-model/debugging.rst
index bbb2794340..e13abddae6 100644
--- a/doc/develop/driver-model/debugging.rst
+++ b/doc/develop/driver-model/debugging.rst
@@ -49,7 +49,7 @@ to see errors. Common ones are:
      of_to_plat() method in the driver.
 
 If there is no error, you should check if the device is actually bound. Call
-dm_dump_all() just before you locate the device to make sure it exists.
+dm_dump_tree() just before you locate the device to make sure it exists.
 
 If it does not exist, check your device tree compatible strings match up with
 what the driver expects (in the struct udevice_id array).
-- 
2.34.1

Re: [PATCH] doc: Replace dm_dump_all() with dm_dump_tree()

[Mattijs Korpershoek]

Hi Dylan,

Thank you for your patch.

On jeu., oct. 19, 2023 at 10:02, Dylan Corrales <deathcamel58@gmail.com> wrote:

> Replace dm_dump_all() with dm_dump_tree() in driver model documentation,
> to reflect changes introduced in commit 145287040480 ("dm: core: Rename
> dm_dump_all()").
>
> Signed-off-by: Dylan Corrales <deathcamel58@gmail.com>

Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>

> ---
>
>  doc/develop/driver-model/debugging.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/develop/driver-model/debugging.rst b/doc/develop/driver-model/debugging.rst
> index bbb2794340..e13abddae6 100644
> --- a/doc/develop/driver-model/debugging.rst
> +++ b/doc/develop/driver-model/debugging.rst
> @@ -49,7 +49,7 @@ to see errors. Common ones are:
>       of_to_plat() method in the driver.
>  
>  If there is no error, you should check if the device is actually bound. Call
> -dm_dump_all() just before you locate the device to make sure it exists.
> +dm_dump_tree() just before you locate the device to make sure it exists.
>  
>  If it does not exist, check your device tree compatible strings match up with
>  what the driver expects (in the struct udevice_id array).
> -- 
> 2.34.1