linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Marco Pagani <marpagan@redhat.com>,
	Moritz Fischer <mdf@kernel.org>, Wu Hao <hao.wu@intel.com>,
	Xu Yilun <yilun.xu@intel.com>, Tom Rix <trix@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org
Subject: Re: [RFC PATCH 1/2] fpga: region: fix kernel-doc
Date: Thu, 6 Jul 2023 14:30:34 -0700	[thread overview]
Message-ID: <e5dae9f1-8492-3046-f694-80d13c9927e9@infradead.org> (raw)
In-Reply-To: <20230706142755.124879-2-marpagan@redhat.com>

Hi--

On 7/6/23 07:27, Marco Pagani wrote:
> - Fix the following warnings issued by the kernel-doc script:
> 
> drivers/fpga/fpga-region.c:46: warning: No description found for return value of 'fpga_region_get'
> drivers/fpga/fpga-region.c:97: warning: No description found for return value of 'fpga_region_program_fpga'
> drivers/fpga/fpga-region.c:295: warning: No description found for return value of 'fpga_region_init'
> 
> - Remove the "and registers a reconfig notifier" part from the description
>   of fpga_region_init() since it does not register an of_overlay notifier
>   anymore.
> 
> - Remove the outdated "if @np is not an FPGA Region" case from the return
>   description of fpga_region_get() and replace it with the case when
>   try_module_get() fails.
> 
> Signed-off-by: Marco Pagani <marpagan@redhat.com>

Looks good. Thanks.

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

> ---
>  drivers/fpga/fpga-region.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c
> index ccf6fdab1360..c9d065a6961b 100644
> --- a/drivers/fpga/fpga-region.c
> +++ b/drivers/fpga/fpga-region.c
> @@ -38,9 +38,10 @@ EXPORT_SYMBOL_GPL(fpga_region_class_find);
>   *
>   * Caller should call fpga_region_put() when done with region.
>   *
> - * Return fpga_region struct if successful.
> - * Return -EBUSY if someone already has a reference to the region.
> - * Return -ENODEV if @np is not an FPGA Region.
> + * Return:
> + * * fpga_region struct if successful.
> + * * -EBUSY if someone already has a reference to the region.
> + * * -ENODEV if can't take parent driver module refcount.
>   */
>  static struct fpga_region *fpga_region_get(struct fpga_region *region)
>  {
> @@ -91,7 +92,7 @@ static void fpga_region_put(struct fpga_region *region)
>   * The caller will need to call fpga_bridges_put() before attempting to
>   * reprogram the region.
>   *
> - * Return 0 for success or negative error code.
> + * Return: 0 for success or negative error code.
>   */
>  int fpga_region_program_fpga(struct fpga_region *region)
>  {
> @@ -288,8 +289,9 @@ static void fpga_region_dev_release(struct device *dev)
>  }
>  
>  /**
> - * fpga_region_init - init function for fpga_region class
> - * Creates the fpga_region class and registers a reconfig notifier.
> + * fpga_region_init - creates the fpga_region class.
> + *
> + * Return: 0 on success or ERR_PTR() on error.
>   */
>  static int __init fpga_region_init(void)
>  {

-- 
~Randy

  reply	other threads:[~2023-07-06 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 14:27 [RFC PATCH 0/2] fpga: fix kernel-doc warnings and align descriptions for the core components Marco Pagani
2023-07-06 14:27 ` [RFC PATCH 1/2] fpga: region: fix kernel-doc Marco Pagani
2023-07-06 21:30   ` Randy Dunlap [this message]
2023-07-10  8:05     ` Xu Yilun
2023-07-06 14:27 ` [RFC PATCH 2/2] fpga: bridge: " Marco Pagani
2023-07-06 21:35   ` Randy Dunlap
2023-07-06 21:37     ` Randy Dunlap
2023-07-07  8:50     ` Marco Pagani
2023-07-10  8:06       ` Xu Yilun

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=e5dae9f1-8492-3046-f694-80d13c9927e9@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=hao.wu@intel.com \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marpagan@redhat.com \
    --cc=mdf@kernel.org \
    --cc=trix@redhat.com \
    --cc=yilun.xu@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;
as well as URLs for NNTP newsgroup(s).