staging: rtl8723bs: remove redundant comparison with true
PATCH 1/1 staging: rtl8723bs: remove redundant comparison with true
Clean up the checkpatch.pl check: "Using comparison to true is error prone". Evaluating the boolean variable directly is preferred and more idiomatic in the Linux kernel.
--- drivers/staging/rtl8723bs/core/rtw_sta_mgt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/staging/rtl8723bs/core/rtw_sta_mgt.c +1 -1
@@ -531,7 +531,7 @@ u8 rtw_access_ctrl(struct adapter *padapter, u8 *mac_addr) paclnode = list_entry(plist, struct rtw_wlan_acl_node, list);if (!memcmp (paclnode->addr, mac_addr,ETH_ALEN )) -if (paclnode->valid == true) { +if (paclnode->valid) { match = true;break ; }
Signature · 1 line
2.43.0
Greg KH
maintainerQuoted 26 lines · Diego Fernando Mancera Gómez
Clean up the checkpatch.pl check: "Using comparison to true is error prone". Evaluating the boolean variable directly is preferred and more idiomatic in the Linux kernel.
Signed-off-by Diego Fernando Mancera Gómez <[email protected]>--- drivers/staging/rtl8723bs/core/rtw_sta_mgt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)drivers/staging/rtl8723bs/core/rtw_sta_mgt.c +1
-1@@ -531,7 +531,7 @@ u8 rtw_access_ctrl(struct adapter *padapter, u8 *mac_addr) paclnode = list_entry(plist, struct rtw_wlan_acl_node, list);if (!memcmp (paclnode->addr, mac_addr,ETH_ALEN )) -if (paclnode->valid == true) { +if (paclnode->valid) { match = true;break ; }Signature · 1 line
2.43.0
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree.
You are receiving this message because of the following common error(s) as indicated below:
- Your patch did not apply to any known trees that Greg is in control of. Possibly this is because you made it against Linus's tree, not the linux-next tree, which is where all of the development for the next version of the kernel is at. Please refresh your patch against the linux-next tree, or even better yet, the development tree specified in the MAINTAINERS file for the subsystem you are submitting a patch for, and resend it.
If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers.
thanks,
greg k-h's patch email bot