From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Dylan Corrales <deathcamel58@gmail.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Simon Glass <sjg@chromium.org>, Dylan Corrales <deathcamel58@gmail.com>
Subject: Re: [PATCH] doc: Replace dm_dump_all() with dm_dump_tree()
Date: Fri, 20 Oct 2023 09:48:41 +0200 [thread overview]
Message-ID: <87pm19ybs6.fsf@baylibre.com> (raw)
In-Reply-To: <20231019140230.2132338-1-deathcamel58@gmail.com>
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
prev parent reply other threads:[~2023-10-20 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 14:02 [PATCH] doc: Replace dm_dump_all() with dm_dump_tree() Dylan Corrales
2023-10-20 7:48 ` Mattijs Korpershoek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm19ybs6.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=deathcamel58@gmail.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox