From: Dan Carpenter <dan.carpenter@linaro.org>
To: Ian To <onlyian4981@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] staging: rtl8723bs: format comments
Date: Wed, 12 Feb 2025 10:21:39 +0300 [thread overview]
Message-ID: <1052fff0-b503-4b47-9897-fe7c26c14126@stanley.mountain> (raw)
In-Reply-To: <b58a9f5b579e17f70681f8419b54d7d9864d1730.1739001527.git.onlyian4981@gmail.com>
On Sat, Feb 08, 2025 at 12:15:54AM -0800, Ian To wrote:
> Some comments were not formatted correctly. Reported by checkpatch.
>
> Signed-off-by: Ian To <onlyian4981@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_security.c | 102 +++++++++---------
> 1 file changed, 51 insertions(+), 51 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_security.c b/drivers/staging/rtl8723bs/core/rtw_security.c
> index 1e9eff01b1aa..3281751436fd 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_security.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_security.c
> @@ -30,10 +30,10 @@ const char *security_type_str(u8 value)
> /* WEP related ===== */
>
> /*
> - Need to consider the fragment situation
> -*/
> + * Need to consider the fragment situation
> + */
> void rtw_wep_encrypt(struct adapter *padapter, u8 *pxmitframe)
> -{ /* exclude ICV */
> +{ /* exclude ICV */
What does this comment even mean?
> @@ -374,39 +374,38 @@ static void phase1(u16 *p1k, const u8 *tk, const u8 *ta, u32 iv32)
> /* size on the 80-bit block P1K[], using the 128-bit key TK[] */
> for (i = 0; i < PHASE1_LOOP_CNT; i++) {
> /* Each add operation here is mod 2**16 */
> - p1k[0] += _S_(p1k[4] ^ TK16((i&1)+0));
> - p1k[1] += _S_(p1k[0] ^ TK16((i&1)+2));
> - p1k[2] += _S_(p1k[1] ^ TK16((i&1)+4));
> - p1k[3] += _S_(p1k[2] ^ TK16((i&1)+6));
> - p1k[4] += _S_(p1k[3] ^ TK16((i&1)+0));
> + p1k[0] += _S_(p1k[4] ^ TK16((i & 1) + 0));
> + p1k[1] += _S_(p1k[0] ^ TK16((i & 1) + 2));
> + p1k[2] += _S_(p1k[1] ^ TK16((i & 1) + 4));
> + p1k[3] += _S_(p1k[2] ^ TK16((i & 1) + 6));
> + p1k[4] += _S_(p1k[3] ^ TK16((i & 1) + 0));
These aren't comments.
regards,
dan carpenter
next prev parent reply other threads:[~2025-02-12 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 8:15 [PATCH 0/3] Adhere to coding style Ian To
2025-02-08 8:15 ` [PATCH 1/3] staging: rtl8723bs: format comments Ian To
2025-02-12 7:21 ` Dan Carpenter [this message]
2025-02-08 8:15 ` [PATCH 2/3] stagin: rtl8723bs: fix spacing Ian To
2025-02-08 8:15 ` [PATCH 3/3] staging: rtl8723bs: remove extra blank lines Ian To
2025-02-15 16:55 ` [PATCH 0/3] Adhere to coding style Greg KH
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=1052fff0-b503-4b47-9897-fe7c26c14126@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=onlyian4981@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 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®