public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Marcos Andrade <marcosandrade95963@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] staging: rtl8723bs: fix coding style and remove dead code
Date: Mon, 30 Mar 2026 18:01:27 +0200	[thread overview]
Message-ID: <2026033005-savings-prologue-e874@gregkh> (raw)
In-Reply-To: <20260326014221.525368-3-marcosandrade95963@gmail.com>

On Thu, Mar 26, 2026 at 01:42:21AM +0000, Marcos Andrade wrote:
> Fix various coding style issues in rtw_wlan_util.c to align the code
> with the Linux kernel formatting standards.
> 
> Specifically, this patch:
> - Resolves lines exceeding the 80-column limit.
> - Removes redundant and unnecessary parentheses in complex conditionals.
> - Deletes commented-out dead code that clutters the logic.
> - Fixes alignment to correctly match open parentheses.
> 
> These changes improve overall code readability and address multiple
> checks reported by checkpatch.pl. No functional changes are introduced.
> 
> Signed-off-by: Marcos Andrade <marcosandrade95963@gmail.com>
> ---
> 

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch did many different things all at once, making it difficult
  to review.  All Linux kernel patches need to only do one thing at a
  time.  If you need to do multiple things (such as clean up all coding
  style issues in a file/driver), do it in a sequence of patches, each
  one doing only one thing.  This will make it easier to review the
  patches to ensure that they are correct, and to help alleviate any
  merge issues that larger patches can cause.

If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

  reply	other threads:[~2026-03-30 16:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26  1:42 [PATCH 0/2] staging: rtl8723bs: fix boolean logic and clean up coding style Marcos Andrade
2026-03-26  1:42 ` [PATCH 1/2] staging: rtl8723bs: fix coding style issues in core:rtw_wlan_util.c Marcos Andrade
2026-03-30 16:01   ` Greg KH
2026-03-26  1:42 ` [PATCH 2/2] staging: rtl8723bs: fix coding style and remove dead code Marcos Andrade
2026-03-30 16:01   ` Greg KH [this message]
2026-03-30  8:40 ` [PATCH 0/2] staging: rtl8723bs: fix boolean logic and clean up coding style luka.gejak

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=2026033005-savings-prologue-e874@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=marcosandrade95963@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