From: Gaston Gonzalez <gascoar@gmail.com>
To: linux-staging@lists.linux.dev
Cc: dpenkler@gmail.com, gregkh@linuxfoundation.org,
dan.carpenter@linaro.org, arnd@arndb.de,
niharchaithanya@gmail.com, jiapeng.chong@linux.alibaba.com,
linux-kernel@vger.kernel.org, Gaston Gonzalez <gascoar@gmail.com>
Subject: [PATCH 1/4] staging: gpib: fix kernel-doc section for write_loop() function
Date: Tue, 4 Mar 2025 16:25:37 -0300 [thread overview]
Message-ID: <20250304192603.40565-3-gascoar@gmail.com> (raw)
In-Reply-To: <20250304192603.40565-1-gascoar@gmail.com>
Add a colon character in the kernel-doc section of write_loop() in order
'leng' to be picked as argument by the kernel-doc compiler.
This change fix the following warning:
warning: Function parameter or struct member 'leng' not described in
'send_command'
Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
---
drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c b/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
index 50faa0c17617..eeabbdb39057 100644
--- a/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
+++ b/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
@@ -232,7 +232,7 @@ static int write_loop(void *dev, char *msg, int leng)
*
* @board: the gpib_board_struct data area for this gpib interface
* @msg: the byte sequence.
- * @leng the byte sequence length; can be given as zero and is
+ * @leng: the byte sequence length; can be given as zero and is
* computed automatically, but if 'msg' contains a zero byte,
* it has to be given explicitly.
*/
--
2.49.0.rc0
next prev parent reply other threads:[~2025-03-04 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 19:25 [PATCH 0/4] staging: gpib: some cleanups in lpvo_usb_gpib.c Gaston Gonzalez
2025-03-04 19:25 ` Gaston Gonzalez [this message]
2025-03-04 19:25 ` [PATCH 2/4] staging: gpib: fix kernel-doc section for function usb_gpib_interface_clear() Gaston Gonzalez
2025-03-04 19:25 ` [PATCH 3/4] staging: gpib: fix kernel-doc section for usb_gpib_line_status() function Gaston Gonzalez
2025-03-04 19:33 ` Gaston Gonzalez
2025-03-04 19:25 ` [PATCH 4/4] staging: gpib: remove commented-out lines Gaston Gonzalez
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=20250304192603.40565-3-gascoar@gmail.com \
--to=gascoar@gmail.com \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=niharchaithanya@gmail.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