All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Kulikov <nikolayof23@gmail.com>
To: Jennifer Guo <guojy.bj@gmail.com>
Cc: linux-staging@lists.linux.dev, gregkh@linuxfoundation.org
Subject: Re: [PATCH] staging: rtl8723bs: remove unnecessary block comment
Date: Thu, 7 May 2026 17:49:14 +0300	[thread overview]
Message-ID: <afymar3gk9tDjU48@archlinux> (raw)
In-Reply-To: <20260505185431.27037-1-guojy.bj@gmail.com>

On Tue, May 05, 2026 at 11:54:31AM -0700, Jennifer Guo wrote:
> Found a block comment formatting warning in odm_interface.h
> via checkpatch.pl. As far as I can tell, this block comment is no
> longer useful. Hence proposing to remove it.

Typically, a commit message states "why" it should be accepted, not how
you arrived at it. This is described in detail in [1].


> Let me know if I missed anything!

Is this really needed in git log?


[1] https://kernelnewbies.org/PatchPhilosophy

Thanks,
Nikolay


> 
> Signed-off-by: Jennifer Guo <guojy.bj@gmail.com>
> ---
>  drivers/staging/rtl8723bs/hal/odm_interface.h | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/hal/odm_interface.h b/drivers/staging/rtl8723bs/hal/odm_interface.h
> index 400473ca58ca..c3b13f5f37db 100644
> --- a/drivers/staging/rtl8723bs/hal/odm_interface.h
> +++ b/drivers/staging/rtl8723bs/hal/odm_interface.h
> @@ -18,14 +18,6 @@
>  #define _bit_all(_name)			BIT_##_name
>  #define _bit_ic(_name, _ic)		BIT_##_name##_ic
>  
> -/*===================================
> -
> -#define ODM_REG_DIG_11N		0xC50
> -#define ODM_REG_DIG_11AC	0xDDD
> -
> -ODM_REG(DIG)
> -=====================================*/
> -
>  #define _reg_11N(_name)			ODM_REG_##_name##_11N
>  #define _bit_11N(_name)			ODM_BIT_##_name##_11N
>  
> -- 
> 2.34.1
> 

      reply	other threads:[~2026-05-07 14:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 18:54 [PATCH] staging: rtl8723bs: remove unnecessary block comment Jennifer Guo
2026-05-07 14:49 ` Nikolay Kulikov [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=afymar3gk9tDjU48@archlinux \
    --to=nikolayof23@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guojy.bj@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.