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 4/4] staging: gpib: remove commented-out lines
Date: Tue, 4 Mar 2025 16:25:43 -0300 [thread overview]
Message-ID: <20250304192603.40565-9-gascoar@gmail.com> (raw)
In-Reply-To: <20250304192603.40565-1-gascoar@gmail.com>
Remove commented-out code in function write_loop().
Signed-off-by: Gaston Gonzalez <gascoar@gmail.com>
---
drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c | 11 -----------
1 file changed, 11 deletions(-)
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 f7dd0809b06c..bb22ee2cc5e1 100644
--- a/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
+++ b/drivers/staging/gpib/lpvo_usb_gpib/lpvo_usb_gpib.c
@@ -218,18 +218,7 @@ static inline int usec_diff(struct timespec64 *a, struct timespec64 *b)
static int write_loop(void *dev, char *msg, int leng)
{
-// int nchar = 0, val;
-
-// do {
-
return skel_do_write(dev, msg, leng);
-
-// if (val < 1) {
-// return -EIO;
-// }
-// nchar +=val;
-// } while (nchar < leng);
-// return leng;
}
/**
--
2.49.0.rc0
prev parent reply other threads:[~2025-03-04 19:28 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 ` [PATCH 1/4] staging: gpib: fix kernel-doc section for write_loop() function Gaston Gonzalez
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 ` Gaston Gonzalez [this message]
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-9-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