From: Ravi Kumar kairi <kumarkairiravi@gmail.com>
To: dpenkler@gmail.com
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, kuba@kernel.org,
dan.carpenter@linaro.org, rmk+kernel@armlinux.org.uk,
Ravi Kumar Kairi <kumarkairiravi@gmail.com>
Subject: [PATCH 1/4] [PATCH V2 1/4] staging:gpib:agilent_82350b: Fixed spelling error
Date: Mon, 17 Feb 2025 15:35:10 +0530 [thread overview]
Message-ID: <20250217100526.49495-2-kumarkairiravi@gmail.com> (raw)
In-Reply-To: <20250217100526.49495-1-kumarkairiravi@gmail.com>
From: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
fixed havn't -> haven't
Signed-off-by: Ravi Kumar Kairi <kumarkairiravi@gmail.com>
---
drivers/staging/gpib/agilent_82350b/agilent_82350b.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
index 5c62ec24fc..5a74a22015 100644
--- a/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
+++ b/drivers/staging/gpib/agilent_82350b/agilent_82350b.c
@@ -121,7 +121,7 @@ static int agilent_82350b_accel_read(gpib_board_t *board, uint8_t *buffer, size_
writeb(DIRECTION_GPIB_TO_HOST, a_priv->gpib_base + SRAM_ACCESS_CONTROL_REG);
if (retval < 0)
return retval;
- // read last bytes if we havn't received an END yet
+ // read last bytes if we haven't received an END yet
if (*end == 0) {
size_t num_bytes;
// try to make sure we holdoff after last byte read
--
2.48.1
next prev parent reply other threads:[~2025-02-17 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 10:05 [PATCH 0/4] staging:gpib:agilent_82350b:Cleanup and spelling fixes Ravi Kumar kairi
2025-02-17 10:05 ` Ravi Kumar kairi [this message]
2025-02-17 10:31 ` 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=20250217100526.49495-2-kumarkairiravi@gmail.com \
--to=kumarkairiravi@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=dpenkler@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=rmk+kernel@armlinux.org.uk \
/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