From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Daniel Kaehn <kaehndan@gmail.com>
Subject: Re: [PATCH v1 1/1] device property: Clarify description of returned value in some functions
Date: Thu, 9 Mar 2023 15:46:06 +0100 [thread overview]
Message-ID: <ZAnxLj7I7RlWlLuC@kroah.com> (raw)
In-Reply-To: <CAJZ5v0jV_Z04zWGuKoiXR4cMovVW8DRyfdYbcwUV30M12Z0shQ@mail.gmail.com>
On Wed, Feb 22, 2023 at 08:16:15PM +0100, Rafael J. Wysocki wrote:
> On Fri, Feb 17, 2023 at 2:33 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> 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>
>
> Acked-by: Rafael J. Wysocki <rafael@kernel.org>
>
> or please let me know if I need to pick it up.
I can take it, thanks.
greg k-h
prev parent reply other threads:[~2023-03-09 14:49 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
2023-02-22 19:16 ` Rafael J. Wysocki
2023-03-09 14:46 ` Greg Kroah-Hartman [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=ZAnxLj7I7RlWlLuC@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--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