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 2/2] fpga: bridge: fix kernel-doc
Date: Thu, 6 Jul 2023 14:37:37 -0700 [thread overview]
Message-ID: <e44dacf9-3945-312d-0a22-6391d5e67667@infradead.org> (raw)
In-Reply-To: <a3da8412-2e13-6b25-346b-da53414f5dba@infradead.org>
Hi again,
On 7/6/23 14:35, Randy Dunlap wrote:
> HI--
>
> On 7/6/23 07:27, Marco Pagani wrote:
>> Fix the following warnings issued by the kernel-doc script:
>>
>> drivers/fpga/fpga-bridge.c:99: warning: No description found for return value of 'of_fpga_bridge_get'
>> drivers/fpga/fpga-bridge.c:163: warning: No description found for return value of 'fpga_bridges_enable'
>> drivers/fpga/fpga-bridge.c:187: warning: No description found for return value of 'fpga_bridges_disable'
>> drivers/fpga/fpga-bridge.c:238: warning: No description found for return value of 'of_fpga_bridge_get_to_list'
>> drivers/fpga/fpga-bridge.c:268: warning: No description found for return value of 'fpga_bridge_get_to_list'
>>
>> - Extend the return description of of_fpga_bridge_get() to include the
>> case when try_module_get() fails.
>>
>> Signed-off-by: Marco Pagani <marpagan@redhat.com>
>> ---
>> drivers/fpga/fpga-bridge.c | 23 ++++++++++++-----------
>> 1 file changed, 12 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/fpga/fpga-bridge.c b/drivers/fpga/fpga-bridge.c
>> index a6c25dee9cc1..0b76c67c50e5 100644
>> --- a/drivers/fpga/fpga-bridge.c
>> +++ b/drivers/fpga/fpga-bridge.c
>> @@ -87,12 +87,13 @@ static struct fpga_bridge *__fpga_bridge_get(struct device *dev,
>> /**
>> * of_fpga_bridge_get - get an exclusive reference to an fpga bridge
>> *
>> - * @np: node pointer of an FPGA bridge
>> - * @info: fpga image specific information
>> + * @np: node pointer of an FPGA bridge.
>> + * @info: fpga image specific information.
>
> Those are not sentences. There is no reason that a period ('.') is needed
> to end those lines. OTOH, the maintainers can do as they like with it.
>
> The rest looks good. Thanks.
>
> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>
>> *
>> - * Return fpga_bridge struct if successful.
>> - * Return -EBUSY if someone already has a reference to the bridge.
>> - * Return -ENODEV if @np is not an FPGA Bridge.
>> + * Return:
>> + * * fpga_bridge struct pointer if successful.
>> + * * -EBUSY if someone already has a reference to the bridge.
>> + * * -ENODEV if @np is not an FPGA Bridge or can't take parent driver refcount.
>> */
>> struct fpga_bridge *of_fpga_bridge_get(struct device_node *np,
>> struct fpga_image_info *info)
>> @@ -155,9 +156,9 @@ EXPORT_SYMBOL_GPL(fpga_bridge_put);
>> * fpga_bridges_enable - enable bridges in a list
>> * @bridge_list: list of FPGA bridges
>> *
>> - * Enable each bridge in the list. If list is empty, do nothing.
>> + * Enable each bridge in the list. If list is empty, do nothing.
These (multiple) 2-space to 1-space changes also are not necessary but are at the
discretion of the maintainers.
>> *
>> - * Return 0 for success or empty bridge list; return error code otherwise.
>> + * Return: 0 for success or empty bridge list or an error code otherwise.
>> */
>> int fpga_bridges_enable(struct list_head *bridge_list)
>> {
>> @@ -179,9 +180,9 @@ EXPORT_SYMBOL_GPL(fpga_bridges_enable);
>> *
>> * @bridge_list: list of FPGA bridges
>> *
>> - * Disable each bridge in the list. If list is empty, do nothing.
>> + * Disable each bridge in the list. If list is empty, do nothing.
>> *
>> - * Return 0 for success or empty bridge list; return error code otherwise.
>> + * Return: 0 for success or empty bridge list or an error code otherwise.
>> */
>> int fpga_bridges_disable(struct list_head *bridge_list)
>> {
>> @@ -230,7 +231,7 @@ EXPORT_SYMBOL_GPL(fpga_bridges_put);
>> *
>> * Get an exclusive reference to the bridge and it to the list.
>> *
>> - * Return 0 for success, error code from of_fpga_bridge_get() otherwise.
>> + * Return: 0 for success, error code from of_fpga_bridge_get() otherwise.
>> */
>> int of_fpga_bridge_get_to_list(struct device_node *np,
>> struct fpga_image_info *info,
>> @@ -260,7 +261,7 @@ EXPORT_SYMBOL_GPL(of_fpga_bridge_get_to_list);
>> *
>> * Get an exclusive reference to the bridge and it to the list.
>> *
>> - * Return 0 for success, error code from fpga_bridge_get() otherwise.
>> + * Return: 0 for success, error code from fpga_bridge_get() otherwise.
>> */
>> int fpga_bridge_get_to_list(struct device *dev,
>> struct fpga_image_info *info,
>
--
~Randy
next prev parent reply other threads:[~2023-07-06 21:39 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
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 [this message]
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=e44dacf9-3945-312d-0a22-6391d5e67667@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).