linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ankit@web.codeaurora.org, Bhalani@web.codeaurora.org,
	er.ankitbhalani@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	abrahamadekunle50@gmail.com, julia.lawall@inria.fr,
	viro@zeniv.linux.org.uk, dan.carpenter@linaro.org,
	zhaochenguang@kylinos.cn, straube.linux@gmail.com,
	mingo@kernel.org, tglx@linutronix.de,
	philipp.g.hortmann@gmail.com, vivek.balachandhar@gmail.com,
	rodrigo.gobbi.7@gmail.com, hansg@kernel.org, nathan@kernel.org
Subject: Re: [PATCH] staging: rtl8723bs: fix block comment style to match kernel coding guidline
Date: Wed, 8 Oct 2025 12:38:02 +0200	[thread overview]
Message-ID: <2025100823-outshine-evaluate-3be1@gregkh> (raw)
In-Reply-To: <20251001134433.16513-1-er.ankitbhalani@gmail.com>

On Wed, Oct 01, 2025 at 07:14:33PM +0530, Ankit@web.codeaurora.org wrote:
> From: Ankit Bhalani <er.ankitbhalani@gmail.com>
> 
> Update block comments to follow the Linux kernel coding style
> recommendations. This include:
> 
>  - Ensuring proper formatting and alignment for multi-line
>    comments.
> 
> Signed-off-by: Ankit Bhalani <er.ankitbhalani@gmail.com>
> ---
>  .../staging/rtl8723bs/core/rtw_ieee80211.c    |  26 +++--
>  drivers/staging/rtl8723bs/core/rtw_io.c       |  48 ++++-----
>  drivers/staging/rtl8723bs/core/rtw_mlme.c     |  75 ++++++-------
>  drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 102 ++++++++++--------
>  drivers/staging/rtl8723bs/core/rtw_pwrctrl.c  |  10 +-
>  drivers/staging/rtl8723bs/core/rtw_security.c |  87 +++++++--------
>  .../staging/rtl8723bs/core/rtw_wlan_util.c    |   6 +-
>  7 files changed, 186 insertions(+), 168 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/core/rtw_ieee80211.c b/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
> index 53d4c113b19c..c31e64600c0a 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
> @@ -132,9 +132,11 @@ u8 *rtw_set_ie(u8 *pbuf,
>  	return pbuf + len + 2;
>  }
>  
> -/*----------------------------------------------------------------------------
> -index: the information element id index, limit is the limit for search
> ------------------------------------------------------------------------------*/
> +/*
> + * ----------------------------------------------------------------------------
> + * index: the information element id index, limit is the limit for search
> + * ----------------------------------------------------------------------------
> + */
>  u8 *rtw_get_ie(u8 *pbuf, signed int index, signed int *len, signed int limit)

This is an odd format for a function comment.  Can you make this look
more "correct"?  All you are describing here is 2 of the variables and
not what the function does at all.

>  /*
> -* Increase and check if the continual_io_error of this @param dvobjprive is larger than MAX_CONTINUAL_IO_ERR
> -* @return true:
> -* @return false:
> -*/
> + * Increase and check if the continual_io_error of this @param dvobjprive is larger than MAX_CONTINUAL_IO_ERR
> + * @return true:
> + * @return false:

What does these last 2 lines mean?

Again, if you are going to comment a function, let's use the documented
way to do so.

Same with other changes in this patch.

thanks,

greg k-h

      reply	other threads:[~2025-10-08 10:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01 13:44 [PATCH] staging: rtl8723bs: fix block comment style to match kernel coding guidline Ankit
2025-10-08 10:38 ` Greg KH [this message]

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=2025100823-outshine-evaluate-3be1@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Ankit@web.codeaurora.org \
    --cc=Bhalani@web.codeaurora.org \
    --cc=abrahamadekunle50@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=er.ankitbhalani@gmail.com \
    --cc=hansg@kernel.org \
    --cc=julia.lawall@inria.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mingo@kernel.org \
    --cc=nathan@kernel.org \
    --cc=philipp.g.hortmann@gmail.com \
    --cc=rodrigo.gobbi.7@gmail.com \
    --cc=straube.linux@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vivek.balachandhar@gmail.com \
    --cc=zhaochenguang@kylinos.cn \
    /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).