devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Muhammad Muzammil <m.muzzammilashraf@gmail.com>,
	robh+dt@kernel.org, frowand.list@gmail.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: of: Fixed kernel doc warning
Date: Tue, 19 Dec 2023 18:37:23 -0800	[thread overview]
Message-ID: <7e1e12d5-041c-4263-a522-c8079f4ed5a1@infradead.org> (raw)
In-Reply-To: <20231219062317.17650-1-muzammil@dreambigsemi.com>



On 12/18/23 22:23, Muhammad Muzammil wrote:
> From: Muzammil Ashraf <m.muzzammilashraf@gmail.com>
> 
> property.c:1220 : Fixed excess struct member definition warning
> property.c:444 	: Fixed missing a blank line after declarations
> 

Nit: only one of those is a kernel-doc warning.

> Signed-off-by: Muzammil Ashraf <m.muzzammilashraf@gmail.com>
> ---
>  drivers/of/property.c | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/of/property.c b/drivers/of/property.c
> index afdaefbd03f6..641a40cf5cf3 100644
> --- a/drivers/of/property.c
> +++ b/drivers/of/property.c
> @@ -441,6 +441,7 @@ int of_property_read_string(const struct device_node *np, const char *propname,
>  				const char **out_string)
>  {
>  	const struct property *prop = of_find_property(np, propname, NULL);
> +
>  	if (!prop)
>  		return -EINVAL;
>  	if (!prop->length)
> @@ -1217,9 +1218,9 @@ static struct device_node *parse_##fname(struct device_node *np,	     \
>   *
>   * @parse_prop: function name
>   *	parse_prop() finds the node corresponding to a supplier phandle
> - * @parse_prop.np: Pointer to device node holding supplier phandle property
> - * @parse_prop.prop_name: Name of property holding a phandle value
> - * @parse_prop.index: For properties holding a list of phandles, this is the
> + *  parse_prop.np: Pointer to device node holding supplier phandle property
> + *  parse_prop.prop_name: Name of property holding a phandle value
> + *  parse_prop.index: For properties holding a list of phandles, this is the
>   *		      index into the list

Looks good. Thanks.

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

>   * @optional: Describes whether a supplier is mandatory or not
>   * @node_not_dev: The consumer node containing the property is never converted

-- 
#Randy
https://people.kernel.org/tglx/notes-about-netiquette
https://subspace.kernel.org/etiquette.html

  reply	other threads:[~2023-12-20  2:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  6:23 [PATCH] drivers: of: Fixed kernel doc warning Muhammad Muzammil
2023-12-20  2:37 ` Randy Dunlap [this message]
2024-01-03 20:38 ` 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=7e1e12d5-041c-4263-a522-c8079f4ed5a1@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.muzzammilashraf@gmail.com \
    --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).