From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Kaehn <kaehndan@gmail.com>
Subject: Re: [PATCH v1 1/1] device property: Clarify description of returned value in some functions
Date: Fri, 17 Feb 2023 15:47:41 +0200 [thread overview]
Message-ID: <Y++FfYfiE1mLceNk@smile.fi.intel.com> (raw)
In-Reply-To: <20230217133344.79278-1-andriy.shevchenko@linux.intel.com>
On Fri, Feb 17, 2023 at 03:33:44PM +0200, Andy Shevchenko wrote:
> Some of the functions do not provide Return: section on absence of which
> kernel-doc complains. Besides that several functions return the fwnode
> handle with incremented reference count. Add a respective note to make sure
> that the caller decrements it when it's not needed anymore.
>
> While at it, unify the style of the Return: sections.
>
> Reported-by: Daniel Kaehn <kaehndan@gmail.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
>
> v2: rephrased the note, added tag, removed unrelated change
> (all requested by Sakari)
I just realized I have forgotten to bump the version.
I will wait for other comments, and will issue a v3 if needed.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-02-17 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 13:33 [PATCH v1 1/1] device property: Clarify description of returned value in some functions Andy Shevchenko
2023-02-17 13:47 ` Andy Shevchenko [this message]
2023-02-22 19:16 ` Rafael J. Wysocki
2023-03-09 14:46 ` Greg Kroah-Hartman
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=Y++FfYfiE1mLceNk@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kaehndan@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sakari.ailus@linux.intel.com \
/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