mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Rix <trix@redhat.com>
To: Nava kishore Manne <nava.manne@xilinx.com>,
	mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com,
	michal.simek@xilinx.com, linux-fpga@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, git@xilinx.com
Subject: Re: [PATCH v2 3/5] fpga: fpga-mgr: Add missing kernel-doc description
Date: Sat, 26 Mar 2022 10:06:16 -0700	[thread overview]
Message-ID: <1ae23c94-ff10-5033-b3aa-75ec5b755a97@redhat.com> (raw)
In-Reply-To: <20220322082202.2007321-4-nava.manne@xilinx.com>


On 3/22/22 1:22 AM, Nava kishore Manne wrote:
> Fixed the warnings: Function parameter or member 'xxx' not
> described.

How were the warnings generated ?

Tom

>
> Signed-off-by: Nava kishore Manne <nava.manne@xilinx.com>
> ---
> Changes for v2:
> 		-Replaced s/@return:/Return:/
>
>   drivers/fpga/fpga-mgr.c | 4 ++++
>   1 file changed, 4 insertions(+)
>
> diff --git a/drivers/fpga/fpga-mgr.c b/drivers/fpga/fpga-mgr.c
> index a699cc8e2fa6..0f2b28538f17 100644
> --- a/drivers/fpga/fpga-mgr.c
> +++ b/drivers/fpga/fpga-mgr.c
> @@ -730,6 +730,8 @@ static void devm_fpga_mgr_unregister(struct device *dev, void *res)
>    * @parent:	fpga manager device from pdev
>    * @info:	parameters for fpga manager
>    *
> + * Return:  fpga manager pointer on success, negative error code otherwise.
> + *
>    * This is the devres variant of fpga_mgr_register_full() for which the unregister
>    * function will be called automatically when the managing device is detached.
>    */
> @@ -763,6 +765,8 @@ EXPORT_SYMBOL_GPL(devm_fpga_mgr_register_full);
>    * @mops:	pointer to structure of fpga manager ops
>    * @priv:	fpga manager private data
>    *
> + * Return:  fpga manager pointer on success, negative error code otherwise.
> + *
>    * This is the devres variant of fpga_mgr_register() for which the
>    * unregister function will be called automatically when the managing
>    * device is detached.


  reply	other threads:[~2022-03-26 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  8:21 [PATCH v2 0/5] fpga: fix for coding style and kernel-doc issues Nava kishore Manne
2022-03-22  8:21 ` [PATCH v2 1/5] fpga: zynq: Fix incorrect variable type Nava kishore Manne
2022-03-26 16:54   ` Tom Rix
2022-04-01 15:45     ` Nava kishore Manne
2022-03-22  8:21 ` [PATCH v2 2/5] fpga: fpga-mgr: fix for coding style issues Nava kishore Manne
2022-03-26 17:03   ` Tom Rix
2022-04-01 15:47     ` Nava kishore Manne
2022-03-22  8:22 ` [PATCH v2 3/5] fpga: fpga-mgr: Add missing kernel-doc description Nava kishore Manne
2022-03-26 17:06   ` Tom Rix [this message]
2022-04-01 15:50     ` Nava kishore Manne
2022-03-22  8:22 ` [PATCH v2 4/5] fpga: Use tab instead of spaces for indentation Nava kishore Manne
2022-03-26 17:08   ` Tom Rix
2022-04-01 15:51     ` Nava kishore Manne
2022-03-22  8:22 ` [PATCH v2 5/5] fpga: fpga-region: Add missing kernel-doc description Nava kishore Manne

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=1ae23c94-ff10-5033-b3aa-75ec5b755a97@redhat.com \
    --to=trix@redhat.com \
    --cc=git@xilinx.com \
    --cc=hao.wu@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fpga@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdf@kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=nava.manne@xilinx.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

all inboxes | Powered by JetHome®