From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: gregkh@linuxfoundation.org, arnd@arndb.de, lee.jones@linaro.org,
kuba@kernel.org, johannes@sipsolutions.net,
unixbhaskar@gmail.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Cc: rdunlap@infradead.org
Subject: [PATCH] staging: wimax: i2400m: Mundane typos fix in the file tx.c
Date: Fri, 12 Mar 2021 17:12:07 +0530 [thread overview]
Message-ID: <20210312114207.3624-1-unixbhaskar@gmail.com> (raw)
s/exahusted/exhausted/
s/caleed/called/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
drivers/staging/wimax/i2400m/tx.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wimax/i2400m/tx.c b/drivers/staging/wimax/i2400m/tx.c
index e9436212fe54..2d15de653951 100644
--- a/drivers/staging/wimax/i2400m/tx.c
+++ b/drivers/staging/wimax/i2400m/tx.c
@@ -85,7 +85,7 @@
* can keep adding payloads to it.
*
* Closed: we are not appending more payloads to this TX message
- * (exahusted space in the queue, too many payloads or
+ * (exhausted space in the queue, too many payloads or
* whichever). We have appended padding so the whole message
* length is aligned to i2400m->bus_tx_block_size (as set by the
* bus/transport layer).
@@ -295,7 +295,7 @@ enum {
/*
* Calculate how much tail room is available
*
- * Note the trick here. This path is ONLY caleed for Case A (see
+ * Note the trick here. This path is ONLY called for Case A (see
* i2400m_tx_fifo_push() below), where we have:
*
* Case A
--
2.26.2
next reply other threads:[~2021-03-12 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 11:42 Bhaskar Chowdhury [this message]
2021-03-12 16:42 ` Randy Dunlap
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=20210312114207.3624-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/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
Powered by JetHome