From: hanyu001@208suo.com
To: stf_xl@wp.pl, helmut.schaa@googlemail.com, kvalo@kernel.org
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] wireless: ralink: rt2x00: Remove unnecessary spaces
Date: Fri, 21 Jul 2023 17:37:59 +0800 [thread overview]
Message-ID: <c0f897b57f6b05d26f2c006154fa15ed@208suo.com> (raw)
In-Reply-To: <tencent_0AFA418AB6A31D66F3B0481E8BC58A70A108@qq.com>
Fix checkpatch warnings:
./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:168: ERROR: space
prohibited after that open parenthesis '('
./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:168: ERROR: space
prohibited before that close parenthesis ')'
./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:169: ERROR: space
prohibited after that open parenthesis '('
./drivers/net/wireless/ralink/rt2x00/rt2x00reg.h:169: ERROR: space
prohibited before that close parenthesis ')'
Signed-off-by: Yu Han <hanyu001@208suo.com>
---
drivers/net/wireless/ralink/rt2x00/rt2x00reg.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/wireless/ralink/rt2x00/rt2x00reg.h
b/drivers/net/wireless/ralink/rt2x00/rt2x00reg.h
index ffe802b..0e5094a 100644
--- a/drivers/net/wireless/ralink/rt2x00/rt2x00reg.h
+++ b/drivers/net/wireless/ralink/rt2x00/rt2x00reg.h
@@ -165,8 +165,8 @@ struct rt2x00_field32 {
* Note that we cannot use the is_power_of_2() function since this
* check must be done at compile-time.
*/
-#define is_power_of_two(x) ( !((x) & ((x)-1)) )
-#define low_bit_mask(x) ( ((x)-1) & ~(x) )
+#define is_power_of_two(x) (!((x) & ((x)-1)))
+#define low_bit_mask(x) (((x)-1) & ~(x))
#define is_valid_mask(x) is_power_of_two(1LU + (x) +
low_bit_mask(x))
/*
next parent reply other threads:[~2023-07-21 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_0AFA418AB6A31D66F3B0481E8BC58A70A108@qq.com>
2023-07-21 9:37 ` hanyu001 [this message]
2023-07-21 10:45 ` Kalle Valo
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=c0f897b57f6b05d26f2c006154fa15ed@208suo.com \
--to=hanyu001@208suo.com \
--cc=helmut.schaa@googlemail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stf_xl@wp.pl \
/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®