From: Jakub Kicinski <kuba@kernel.org>
To: Kriish Sharma <kriish.sharma2006@gmail.com>
Cc: Ivan Vecera <ivecera@redhat.com>,
Prathosh Satish <Prathosh.Satish@microchip.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dpll: zl3073x: fix kernel-doc name and missing parameter in fw.c
Date: Tue, 11 Nov 2025 17:42:34 -0800 [thread overview]
Message-ID: <20251111174234.53be1a97@kernel.org> (raw)
In-Reply-To: <20251110195030.2248235-1-kriish.sharma2006@gmail.com>
On Mon, 10 Nov 2025 19:50:30 +0000 Kriish Sharma wrote:
> Documentation build reported:
What do you mean by "documentation build"? make htmldocs?
> Warning: drivers/dpll/zl3073x/fw.c:365 function parameter 'comp' not described in 'zl3073x_fw_component_flash'
> Warning: drivers/dpll/zl3073x/fw.c:365 expecting prototype for zl3073x_flash_bundle_flash(). Prototype was for zl3073x_fw_component_flash() instead
>
> The kernel-doc comment above `zl3073x_fw_component_flash()` used the wrong
> function name (`zl3073x_flash_bundle_flash`) and omitted the `@comp` parameter.
> This patch updates the comment to correctly document the
> `zl3073x_fw_component_flash()` function and its arguments.
>
> Fixes: ca017409da69 ("dpll: zl3073x: Add firmware loading functionality")
> Signed-off-by: Kriish Sharma <kriish.sharma2006@gmail.com>
> ---
> drivers/dpll/zl3073x/fw.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dpll/zl3073x/fw.c b/drivers/dpll/zl3073x/fw.c
> index def37fe8d9b0..ca5210c0829d 100644
> --- a/drivers/dpll/zl3073x/fw.c
> +++ b/drivers/dpll/zl3073x/fw.c
> @@ -352,9 +352,9 @@ struct zl3073x_fw *zl3073x_fw_load(struct zl3073x_dev *zldev, const char *data,
> }
>
> /**
> - * zl3073x_flash_bundle_flash - Flash all components
> + * zl3073x_fw_component_flash - Flash all components
> * @zldev: zl3073x device structure
> - * @components: pointer to components array
> + * @comp: pointer to components array
> * @extack: netlink extack pointer to report errors
> *
> * Returns 0 in case of success or negative number otherwise.
This now makes the kernel-doc script realize that the return value is
not documented. Please also add a : after the Returns on the last line
--
pw-bot: cr
next prev parent reply other threads:[~2025-11-12 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 19:50 [PATCH] dpll: zl3073x: fix kernel-doc name and missing parameter in fw.c Kriish Sharma
2025-11-10 19:59 ` Ivan Vecera
2025-11-12 1:42 ` Jakub Kicinski [this message]
2025-11-12 4:24 ` Kriish Sharma
2025-11-12 14:16 ` Jakub Kicinski
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=20251111174234.53be1a97@kernel.org \
--to=kuba@kernel.org \
--cc=Prathosh.Satish@microchip.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kriish.sharma2006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vadim.fedorenko@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.