From: Sandeep Salwan <salwansandeep5@gmail.com>
To: gregkh@linuxfoundation.org, dan.carpenter@linaro.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Sandeep Salwan <salwansandeep5@gmail.com>
Subject: [PATCH] staging: gpib: Remove commented-out debug code (v3) Code cleanup. This code has some debug code which is commented out. Delete it.
Date: Thu, 9 Jan 2025 17:45:36 -0500 [thread overview]
Message-ID: <20250109224536.3531-1-salwansandeep5@gmail.com> (raw)
Signed-off-by: Sandeep Salwan <salwansandeep5@gmail.com>
---
v3: remove leftover braces, re-write commit message
v2: removed commented-out code only
---
drivers/staging/gpib/agilent_82350b/agilent_82350b.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
index 53006d0cc79c..fd05f15a683e 100644
--- a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
+++ b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
@@ -30,11 +30,8 @@ int agilent_82350b_accel_read(gpib_board_t *board, uint8_t *buffer, size_t lengt
unsigned short event_status;
int i, num_fifo_bytes;
//hardware doesn't support checking for end-of-string character when using fifo
- if (tms_priv->eos_flags & REOS) {
- //pr_info("ag-rd: using tms9914 read for REOS %x EOS %x\n",tms_priv->eos_flags,
- // tms_priv->eos);
+ if (tms_priv->eos_flags & REOS)
return tms9914_read(board, tms_priv, buffer, length, end, bytes_read);
- }
clear_bit(DEV_CLEAR_BN, &tms_priv->state);
--
2.47.1
next reply other threads:[~2025-01-09 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 22:45 Sandeep Salwan [this message]
2025-01-10 5:58 ` [PATCH] staging: gpib: Remove commented-out debug code (v3) Code cleanup. This code has some debug code which is commented out. Delete it Greg KH
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=20250109224536.3531-1-salwansandeep5@gmail.com \
--to=salwansandeep5@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.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.