From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: gregkh@linuxfoundation.org, colin.king@canonical.com,
unixbhaskar@gmail.com, davem@davemloft.net, lee.jones@linaro.org,
arnd@arndb.de, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] staging: wimax: Mundane typo fixes
Date: Tue, 23 Mar 2021 06:36:07 +0530 [thread overview]
Message-ID: <20210323010607.3918516-1-unixbhaskar@gmail.com> (raw)
s/procesing/processing/
s/comunication/communication/
Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
---
drivers/staging/wimax/i2400m/driver.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/wimax/i2400m/driver.c b/drivers/staging/wimax/i2400m/driver.c
index f5186458bb3d..162a92682977 100644
--- a/drivers/staging/wimax/i2400m/driver.c
+++ b/drivers/staging/wimax/i2400m/driver.c
@@ -96,7 +96,7 @@ MODULE_PARM_DESC(barkers,
*
* This function just verifies that the header declaration and the
* payload are consistent and then deals with it, either forwarding it
- * to the device or procesing it locally.
+ * to the device or processing it locally.
*
* In the i2400m, messages are basically commands that will carry an
* ack, so we use i2400m_msg_to_dev() and then deliver the ack back to
@@ -835,7 +835,7 @@ EXPORT_SYMBOL_GPL(i2400m_reset);
*
* Returns: 0 if ok, < 0 errno code on error.
*
- * Sets up basic device comunication infrastructure, boots the ROM to
+ * Sets up basic device communication infrastructure, boots the ROM to
* read the MAC address, registers with the WiMAX and network stacks
* and then brings up the device.
*/
--
2.31.0
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next reply other threads:[~2021-03-23 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 1:06 Bhaskar Chowdhury [this message]
2021-03-23 4:14 ` [PATCH] staging: wimax: Mundane typo fixes Randy Dunlap
2021-03-23 4:48 ` Bhaskar Chowdhury
2021-03-23 7:13 ` 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=20210323010607.3918516-1-unixbhaskar@gmail.com \
--to=unixbhaskar@gmail.com \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).