Linux kernel staging patches
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Gowtham S Bhushan <gowtham398gs@gmail.com>
Cc: Ethan Tidmore <ethantidmore06@gmail.com>,
	Dan Carpenter <error27@gmail.com>,
	Lin YuChen <starpt.official@gmail.com>,
	Maksym Pikhotskyi <mpikhotskyi@gmail.com>,
	Sameeksha Sankpal <sameekshasankpal@gmail.com>,
	Artur Stupa <arthur.stupa@gmail.com>,
	Archit Anant <architanant5@gmail.com>,
	"open list:STAGING SUBSYSTEM" <linux-staging@lists.linux.dev>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: rtl8723bs: avoid linelength > 100 in rtw_security
Date: Thu, 1 Oct 2026 07:44:26 +0200	[thread overview]
Message-ID: <2026100105-hangout-cannabis-36f2@gregkh> (raw)
In-Reply-To: <20260911054908.37690-1-gowtham398gs@gmail.com>

On Fri, Sep 11, 2026 at 11:19:02AM +0530, Gowtham S Bhushan wrote:
> Signed-off-by: Gowtham S Bhushan <gowtham398gs@gmail.com>
> ---
>  drivers/staging/rtl8723bs/core/rtw_security.c | 29 ++++++++++++-------
>  1 file changed, 18 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/staging/rtl8723bs/core/rtw_security.c b/drivers/staging/rtl8723bs/core/rtw_security.c
> index 2217cffac5f2..e82392938805 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_security.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_security.c
> @@ -34,7 +34,7 @@ const char *security_type_str(u8 value)
>  
>  /* Need to consider the fragment  situation */
>  void rtw_wep_encrypt(struct adapter *padapter, u8 *pxmitframe)
> -{																	/*  exclude ICV */
> +{					/*  exclude ICV */

Why is the comment indented like that?  That's very odd, don't you
think?

And there was no changelog text :(

thanks,

greg k-h

      reply	other threads:[~2026-10-01  5:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  5:49 [PATCH] staging: rtl8723bs: avoid linelength > 100 in rtw_security Gowtham S Bhushan
2026-10-01  5:44 ` Greg Kroah-Hartman [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=2026100105-hangout-cannabis-36f2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=architanant5@gmail.com \
    --cc=arthur.stupa@gmail.com \
    --cc=error27@gmail.com \
    --cc=ethantidmore06@gmail.com \
    --cc=gowtham398gs@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=mpikhotskyi@gmail.com \
    --cc=sameekshasankpal@gmail.com \
    --cc=starpt.official@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