From: Randy Dunlap <rdunlap@infradead.org>
To: Aditya Bansal <adbansal99@gmail.com>, gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: wfx: fixed misspelled word in comment
Date: Tue, 4 Aug 2020 08:24:39 -0700 [thread overview]
Message-ID: <bc993561-e494-d6b5-fc73-eb56cb496d75@infradead.org> (raw)
In-Reply-To: <20200804145816.GA3823@aditya>
On 8/4/20 7:58 AM, Aditya Bansal wrote:
> From: Aditya Bansal <adbansal99@gmail.com>
>
> Subject: [PATCH] fixed typo in driver/staging/wfx/hif_tx.c file
>
> Correct the spelling of function
>
> Signed-off-by: Aditya Bansal <adbansal99@gmail.com>
> ---
>
> diff --git a/drivers/staging/wfx/hif_tx.c b/drivers/staging/wfx/hif_tx.c
> index 5110f9b93762..6a485fa5b72b 100644
> --- a/drivers/staging/wfx/hif_tx.c
> +++ b/drivers/staging/wfx/hif_tx.c
> @@ -125,7 +125,7 @@ int wfx_cmd_send(struct wfx_dev *wdev, struct hif_msg *request,
>
> // This function is special. After HIF_REQ_ID_SHUT_DOWN, chip won't reply to any
> // request anymore. We need to slightly hack struct wfx_hif_cmd for that job. Be
> -// carefull to only call this funcion during device unregister.
> +// carefull to only call this function during device unregister.
careful
> int hif_shutdown(struct wfx_dev *wdev)
> {
> int ret;
--
~Randy
next prev parent reply other threads:[~2020-08-04 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 14:58 [PATCH] staging: wfx: fixed misspelled word in comment Aditya Bansal
2020-08-04 12:47 ` [PATCH v2] " Aditya Bansal
2020-08-18 13:58 ` Greg KH
2020-08-04 15:24 ` Randy Dunlap [this message]
2020-08-04 15:43 ` [PATCH] " Joe Perches
2020-08-04 10:37 ` Aditya Bansal
2020-08-04 16:23 ` Joe Perches
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=bc993561-e494-d6b5-fc73-eb56cb496d75@infradead.org \
--to=rdunlap@infradead.org \
--cc=adbansal99@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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).