linux-kernel - Re: [PATCH] staging: rtl8723bs: include: Fix spelling mistake in rtw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1d480b00-de7c-490e-8042-2d2c865ddbf0@gmail.com>
Date: Sat, 7 Sep 2024 07:33:57 +0200
From: Philipp Hortmann <philipp.g.hortmann@...il.com>
To: Roshan Khatri <topofeverest8848@...il.com>, gregkh@...uxfoundation.org
Cc: linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: include: Fix spelling mistake in
 rtw_mlme.h

On 9/6/24 16:11, Roshan Khatri wrote:
> This patch fixes spelling mistake to increase code readability
> and searching.
> 
> Signed-off-by: Roshan Khatri <topofeverest8848@...il.com>
> ---
>   drivers/staging/rtl8723bs/include/rtw_mlme.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/rtl8723bs/include/rtw_mlme.h b/drivers/staging/rtl8723bs/include/rtw_mlme.h
> index e103c4a15d1a..e665479babc2 100644
> --- a/drivers/staging/rtl8723bs/include/rtw_mlme.h
> +++ b/drivers/staging/rtl8723bs/include/rtw_mlme.h
> @@ -131,7 +131,7 @@ struct mlme_priv {
>   	u8 roam_rssi_diff_th; /* rssi difference threshold for active scan candidate selection */
>   	u32 roam_scan_int_ms; /* scan interval for active roam */
>   	u32 roam_scanr_exp_ms; /* scan result expire time in ms  for roam */
> -	u8 roam_tgt_addr[ETH_ALEN]; /* request to roam to speicific target without other consideration */
> +	u8 roam_tgt_addr[ETH_ALEN]; /* request to roam to specific target without other consideration */
>   
>   	u8 *nic_hdl;
>   

Hi Roshan,

please make a patch series out of this 4 emails. This makes handling 
easier for the maintainer and the reviewers.

If you send in a second version of this patch please use a change 
history. Description from Dan under:
https://staticthinking.wordpress.com/2022/07/27/how-to-send-a-v2-patch/

Thanks for your support.

Bye Philipp