linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Artur Stupa <arthur.stupa@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: rtl8723bs: core: fix block comment style issues
Date: Thu, 20 Nov 2025 10:22:35 +0300	[thread overview]
Message-ID: <aR7Bu4ared9jg1ag@stanley.mountain> (raw)
In-Reply-To: <20251120002948.23153-1-arthur.stupa@gmail.com>

On Wed, Nov 19, 2025 at 04:29:21PM -0800, Artur Stupa wrote:
> +/*
> + **********************************************************************

I was going to ignore this ************** line, but

> + * Routine: Phase 1 -- generate P1K, given TA, TK, IV32
> + *
> + * Inputs:
> + *     tk[]      = temporal key                         [128 bits]
> + *     ta[]      = transmitter's MAC address            [ 48 bits]
> + *     iv32      = upper 32 bits of IV                  [ 32 bits]
> + * Output:
> + *     p1k[]     = Phase 1 key                          [ 80 bits]
> + *
> + * Note:
> + *     This function only needs to be called every 2**16 packets,
> + *     although in theory it could be called every packet.
> + *
> + **********************************************************************
> + */
>  static void phase1(u16 *p1k, const u8 *tk, const u8 *ta, u32 iv32)
>  {
>  	signed int  i;

[ snip ]

> diff --git a/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c b/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
> index d1f6030799cb..2014998245db 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
> @@ -385,10 +385,10 @@ u32 rtw_free_stainfo(struct adapter *padapter, struct sta_info *psta)
>  	rtw_release_macid(pstapriv->padapter, psta);
>  
>  /*
> -	spin_lock_bh(&pstapriv->asoc_list_lock);
> -	list_del_init(&psta->asoc_list);
> -	spin_unlock_bh(&pstapriv->asoc_list_lock);
> -*/
> + * spin_lock_bh(&pstapriv->asoc_list_lock);
> + * list_del_init(&psta->asoc_list);
> + * spin_unlock_bh(&pstapriv->asoc_list_lock);
> + */

I had to complain about this.  Please, delete commented out code.

To be honest, it would be better to break this up into two patches, one
which deletes dead code and the other which changes the comment formats.
I wouldn't have said anything about that if it hadn't been for this
dead code.

regards,
dan carpenter


  reply	other threads:[~2025-11-20 10:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  6:26 [PATCH] staging: rtl8723bs: core: fix block comment style issues Artur Stupa
2025-11-19 11:36 ` Dan Carpenter
2025-11-20  0:29 ` [PATCH v2] " Artur Stupa
2025-11-20  7:22   ` Dan Carpenter [this message]
2025-11-20 20:30   ` [PATCH v3 1/2] " Artur Stupa
2025-11-20 20:30     ` [PATCH v3 2/2] staging: rtl8723bs: core: delete commented-out code Artur Stupa
2025-11-21  6:59     ` [PATCH v3 1/2] staging: rtl8723bs: core: fix block comment style issues Greg KH
2025-11-21 22:41     ` [PATCH v4 " Artur Stupa
2025-11-21 22:41       ` [PATCH v4 2/2] staging: rtl8723bs: core: delete commented-out code Artur Stupa
2025-11-24  7:58       ` [PATCH v4 1/2] staging: rtl8723bs: core: fix block comment style issues Dan Carpenter

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=aR7Bu4ared9jg1ag@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=arthur.stupa@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    /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;
as well as URLs for NNTP newsgroup(s).