devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Documentation inconsistency
@ 2016-08-01 19:55 Mirza Krak
       [not found] ` <CALw8SCUjiKsAoNVxORkwyrDztEAGYd-zdCGpj6UJHjskppuROQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Mirza Krak @ 2016-08-01 19:55 UTC (permalink / raw)
  To: robh+dt-DgEjT+Ai2ygdnm+yROfE0A,
	frowand.list-Re5JQEeQqe8AvxtiuMwx3w,
	grant.likely-QSEj5FYQhm4dnm+yROfE0A
  Cc: devicetree-u79uwXL29TY76Z2rM5mHXA

Hi all.

Came across a small documentation regression.

In 75f353b61342 ("of/platform: Fix of_platform_device_destroy
iteration of devices") return value was removed from
of_platform_depopulate but documentation brief was not updated.

/**
 * of_platform_depopulate() - Remove devices populated from device tree
 * @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
 * created from their respective device tree nodes (and only those,
 * leaving others - eg. manually created - unharmed).
 *
 * Returns 0 when all children devices have been removed or
 * -EBUSY when some children remained.
 */
void of_platform_depopulate(struct device *parent)

I could send a patch removing the "return" part, but I am not sure if
the rest of the brief needs some updating.

Best Regards
Mirza
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Documentation inconsistency
       [not found] ` <CALw8SCUjiKsAoNVxORkwyrDztEAGYd-zdCGpj6UJHjskppuROQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2016-08-01 21:04   ` Frank Rowand
  0 siblings, 0 replies; 2+ messages in thread
From: Frank Rowand @ 2016-08-01 21:04 UTC (permalink / raw)
  To: Mirza Krak, robh+dt-DgEjT+Ai2ygdnm+yROfE0A,
	grant.likely-QSEj5FYQhm4dnm+yROfE0A
  Cc: devicetree-u79uwXL29TY76Z2rM5mHXA

On 08/01/16 12:55, Mirza Krak wrote:
> Hi all.
> 
> Came across a small documentation regression.
> 
> In 75f353b61342 ("of/platform: Fix of_platform_device_destroy
> iteration of devices") return value was removed from
> of_platform_depopulate but documentation brief was not updated.
> 
> /**
>  * of_platform_depopulate() - Remove devices populated from device tree
>  * @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
>  * created from their respective device tree nodes (and only those,
>  * leaving others - eg. manually created - unharmed).
>  *
>  * Returns 0 when all children devices have been removed or
>  * -EBUSY when some children remained.
>  */
> void of_platform_depopulate(struct device *parent)
> 
> I could send a patch removing the "return" part, but I am not sure if
> the rest of the brief needs some updating.
> 
> Best Regards
> Mirza
> 

Hi Mirza,

Thanks for pointing that out.  But no need for a patch.  I've been going
through all of the docbook headers (which have much breakage) and will
be updating them.

-Frank
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-08-01 21:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-08-01 19:55 Documentation inconsistency Mirza Krak
     [not found] ` <CALw8SCUjiKsAoNVxORkwyrDztEAGYd-zdCGpj6UJHjskppuROQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-08-01 21:04   ` Frank Rowand

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).