From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Roshan Khatri <topofeverest8848@gmail.com>,
Larry.Finger@lwfinger.net, florian.c.schilhabel@googlemail.com,
gregkh@linuxfoundation.org, ayushtiw0110@gmail.com,
namcaov@gmail.com, dan.carpenter@linaro.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8712: Fix spelling mistake in rtl871x_mlme.c
Date: Mon, 27 May 2024 09:50:55 +0200 [thread overview]
Message-ID: <7345af0c-945f-417d-bf18-33a4cdb66df0@gmail.com> (raw)
In-Reply-To: <20240524154001.63946-1-topofeverest8848@gmail.com>
On 24.05.24 17:40, Roshan Khatri wrote:
> This patch corrects misspelled word to increase code readability and
> searching.
>
> Signed-off-by: Roshan Khatri <topofeverest8848@gmail.com>
> ---
> drivers/staging/rtl8712/rtl871x_mlme.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/rtl8712/rtl871x_mlme.c b/drivers/staging/rtl8712/rtl871x_mlme.c
> index fccfa0915a02..70c295e97068 100644
> --- a/drivers/staging/rtl8712/rtl871x_mlme.c
> +++ b/drivers/staging/rtl8712/rtl871x_mlme.c
> @@ -944,7 +944,7 @@ void r8712_cpwm_event_callback(struct _adapter *adapter, u8 *pbuf)
>
> /* When the Netgear 3500 AP is with WPA2PSK-AES mode, it will send
> * the ADDBA req frame with start seq control = 0 to wifi client after
> - * the WPA handshake and the seqence number of following data packet
> + * the WPA handshake and the sequence number of following data packet
> * will be 0. In this case, the Rx reorder sequence is not longer than 0
> * and the WiFi client will drop the data with seq number 0.
> * So, the 8712 firmware has to inform driver with receiving the
Reviewed-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
prev parent reply other threads:[~2024-05-27 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 15:40 [PATCH] staging: rtl8712: Fix spelling mistake in rtl871x_mlme.c Roshan Khatri
2024-05-27 7:50 ` Philipp Hortmann [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=7345af0c-945f-417d-bf18-33a4cdb66df0@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=ayushtiw0110@gmail.com \
--cc=dan.carpenter@linaro.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcaov@gmail.com \
--cc=topofeverest8848@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.