devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Johan Hovold <johan+linaro@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of: fix recursion typo in kernel doc
Date: Fri, 17 Nov 2023 10:07:57 -0800	[thread overview]
Message-ID: <b478e572-3188-459d-9fa2-1de9ff8a8699@infradead.org> (raw)
In-Reply-To: <20231117171628.20139-1-johan+linaro@kernel.org>



On 11/17/23 09:16, Johan Hovold wrote:
> Fix a typo in the kernel doc for the of_platform_depopulate() functions,
> which remove children "recursively".
> 
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>

Looks good. Thanks.

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  drivers/of/platform.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/of/platform.c b/drivers/of/platform.c
> index 126d265aa7d8..2293059758d1 100644
> --- a/drivers/of/platform.c
> +++ b/drivers/of/platform.c
> @@ -668,7 +668,7 @@ EXPORT_SYMBOL_GPL(of_platform_device_destroy);
>   * @parent: device which children will be removed
>   *
>   * Complementary to of_platform_populate(), this function removes children
> - * of the given device (and, recurrently, their children) that have been
> + * of the given device (and, recursively, their children) that have been
>   * created from their respective device tree nodes (and only those,
>   * leaving others - eg. manually created - unharmed).
>   */
> @@ -737,7 +737,7 @@ static int devm_of_platform_match(struct device *dev, void *res, void *data)
>   * @dev: device that requested to depopulate from device tree data
>   *
>   * Complementary to devm_of_platform_populate(), this function removes children
> - * of the given device (and, recurrently, their children) that have been
> + * of the given device (and, recursively, their children) that have been
>   * created from their respective device tree nodes (and only those,
>   * leaving others - eg. manually created - unharmed).
>   */

-- 
~Randy

  reply	other threads:[~2023-11-17 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 17:16 [PATCH] of: fix recursion typo in kernel doc Johan Hovold
2023-11-17 18:07 ` Randy Dunlap [this message]
2023-11-19 16:10 ` Rob Herring

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=b478e572-3188-459d-9fa2-1de9ff8a8699@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=johan+linaro@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).