public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Ian To <onlyian4981@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] staging: rtl8723bs: format comments
Date: Sat, 15 Feb 2025 17:56:54 +0100	[thread overview]
Message-ID: <2025021510-surround-drainage-1425@gregkh> (raw)
In-Reply-To: <2e6dc11ef35d5af653095e416f2a48b6dbcc0de1.1739351267.git.onlyian4981@gmail.com>

On Wed, Feb 12, 2025 at 01:22: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 | 92 +++++++++----------
>  1 file changed, 46 insertions(+), 46 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/core/rtw_security.c b/drivers/staging/rtl8723bs/core/rtw_security.c
> index 1e9eff01b1aa..f4556ae54352 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 */
> +{
>  	union {
>  		__le32 f0;
>  		unsigned char f1[4];
> @@ -342,23 +342,23 @@ static const unsigned short Sbox1[2][256] = {      /* Sbox for hash (can be in R
>  	}
>  };
>  
> - /*
> -**********************************************************************
> -* 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.
> -*
> -**********************************************************************
> -*/
> +/*
> + **********************************************************************

Why the long line of **** ?

That should not be needed.

> -/**
> +/*

Why are you removing kerneldoc comment style?

>   * omac1_aes_128_vector - One-Key CBC MAC (OMAC1) hash with AES-128
>   * @key: 128-bit key for the hash operation
>   * @num_elem: Number of elements in the data vector
> @@ -1530,7 +1529,7 @@ static int omac1_aes_128_vector(u8 *key, size_t num_elem,
>  	return 0;
>  }
>  
> -/**
> +/*

Same here?

thanks,

greg k-h

  reply	other threads:[~2025-02-15 16:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  9:22 [PATCH v2 0/3] Adhere to coding style Ian To
2025-02-12  9:22 ` [PATCH v2 1/3] staging: rtl8723bs: format comments Ian To
2025-02-15 16:56   ` Greg KH [this message]
2025-02-12  9:22 ` [PATCH v2 2/3] stagin: rtl8723bs: fix spacing Ian To
2025-02-15 16:57   ` Greg KH
2025-02-12  9:22 ` [PATCH v2 3/3] staging: rtl8723bs: remove extra blank lines Ian To
2025-02-15 16:58   ` 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=2025021510-surround-drainage-1425@gregkh \
    --to=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