Linux kernel staging patches
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: Tomasz Unger <tomasz.unger@yahoo.pl>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: rtl8723bs: remove unnecessary parentheses
Date: Mon, 1 Jun 2026 21:29:46 +0300	[thread overview]
Message-ID: <ah3PmjHQDwe-_orU@stanley.mountain> (raw)
In-Reply-To: <20260601-staging-fix-1-v3-1-331ec58683c0@yahoo.pl>

On Mon, Jun 01, 2026 at 08:11:59PM +0200, Tomasz Unger wrote:
> Remove unnecessary parentheses to clear checkpatch.pl warnings
> 
> Example of fixed warnings:
> CHECK: Unnecessary parentheses around dvobj->cam_cache[id]
> CHECK: Unnecessary parentheses around 'val != 0xfe'

This changed in v3.

Btw, how were you even seeing this warning?  I disabled it.  Were
you working against an old tree?

> 
> Checkpatch warnings regarding line length above 100 columns on modified
> lines were also fixed

Please no, that's a separate fix.

> 
> V2->V3:
>   Reverted condition parentheses changes per Dan Carpenter's review:
>   staging rules deliberately silence this checkpatch warning
> 
> Changes in v3:
> - Reverted condition parentheses changes per Dan Carpenter's review
> - Link to v2: https://lore.kernel.org/all/20260531061022.573089-1-mavick4022@gmail.com/
> 

This stuff doesn't belong in the permanent git log.
There are still some changes which should be removed from the commit.

> Signed-off-by: Tomasz Unger <tomasz.unger@yahoo.pl>
> ---
> Changes in v2:
> - EDITME: describe what is new in this series revision.
> - EDITME: use bulletpoints and terse descriptions.
> - Link to v1: https://patch.msgid.link/20260527-staging-fix-1-v1-1-66ad880bcf76@yahoo.pl

Those sorts of comments go here.

> 
> To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: linux-staging@lists.linux.dev
> Cc: linux-kernel@vger.kernel.org

This stuff is fine since it is just discarded but it's also unnecessary.

regards,
dan carpenter



  reply	other threads:[~2026-06-01 18:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260601-staging-fix-1-v3-1-331ec58683c0.ref@yahoo.pl>
2026-06-01 18:11 ` [PATCH v3] staging: rtl8723bs: remove unnecessary parentheses Tomasz Unger
2026-06-01 18:29   ` Dan Carpenter [this message]
2026-05-31  6:10 [PATCH v2] " Eugene Mavick
     [not found] ` <20260603080105.780648-1-m@mavick.dev>
2026-06-03  8:44   ` [PATCH v3] " Dan Carpenter
     [not found]     ` <DIZB2839PXFV.3A5L73XAO2X67@mavick.dev>
2026-06-03 10:18       ` Dan Carpenter

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=ah3PmjHQDwe-_orU@stanley.mountain \
    --to=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=tomasz.unger@yahoo.pl \
    /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