From: Randy Dunlap <rdunlap@infradead.org>
To: Bhaskar Chowdhury <unixbhaskar@gmail.com>,
gregkh@linuxfoundation.org, colin.king@canonical.com,
davem@davemloft.net, johannes@sipsolutions.net, arnd@arndb.de,
lee.jones@linaro.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wimax: i2400m: Mundane typo fix in the file driver.c
Date: Wed, 17 Mar 2021 10:35:30 -0700 [thread overview]
Message-ID: <971c14bd-e755-d1cf-b518-c889e5348f11@infradead.org> (raw)
In-Reply-To: <20210317092624.1138207-1-unixbhaskar@gmail.com>
On 3/17/21 2:26 AM, Bhaskar Chowdhury wrote:
>
> s/procesing/processing/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> drivers/staging/wimax/i2400m/driver.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/wimax/i2400m/driver.c b/drivers/staging/wimax/i2400m/driver.c
> index f5186458bb3d..8091106212f9 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
> --
--
~Randy
prev parent reply other threads:[~2021-03-17 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 9:26 Bhaskar Chowdhury
2021-03-17 17:35 ` Randy Dunlap [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=971c14bd-e755-d1cf-b518-c889e5348f11@infradead.org \
--to=rdunlap@infradead.org \
--cc=arnd@arndb.de \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=unixbhaskar@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
all inboxes | Powered by JetHome®