From: Julia Lawall <julia.lawall@inria.fr>
To: Samuel Abraham <abrahamadekunle50@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
outreachy@lists.linux.dev, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] staging: rtl8723bs: Prevent duplicate NULL tests on a value
Date: Sun, 6 Apr 2025 09:00:26 -0400 (EDT) [thread overview]
Message-ID: <8efaafd9-b01-c52f-4969-31628aa839a7@inria.fr> (raw)
In-Reply-To: <CADYq+fb+L9_S6WDJYKdugCVNCd9kT2QvEURimPHb+_3r-PoADg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Sat, 5 Apr 2025, Samuel Abraham wrote:
> On Sat, Apr 5, 2025 at 2:30 PM Julia Lawall <julia.lawall@inria.fr> wrote:
> >
> >
> >
> > On Sat, 5 Apr 2025, Abraham Samuel Adekunle wrote:
> >
> > > When a value has been tested for NULL in an expression, a
> > > second NULL test on the same value in another expression
> > > is unnecessary when the value has not been assigned to NULL.
> > >
> > > Remove unnecessary duplicate NULL tests on the same value
> > > that has previously been tested.
> > >
> > > Found by Coccinelle.
> >
> > The changes are found in the same way, but the code patterns are overall
> > quite different. It could make sense to make separate patches for them.
> > Then you could make a log message that is really specialized to the code
> > in each patch and it would be easier for the reviewer to be convinced that
> > you have done the right thing.
>
> Thank you for the feedback Julia.
> Okay how about the versioning. Should I make it like a Patchset?
>
> Like [PATCH v6] with the cover letter and two patches, one for each code
> pattern?
Yes. Just explain what you are doing.
julia
next prev parent reply other threads:[~2025-04-06 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 13:21 Abraham Samuel Adekunle
2025-04-05 13:30 ` Julia Lawall
2025-04-05 14:46 ` Samuel Abraham
2025-04-06 13:00 ` Julia Lawall [this message]
2025-04-05 14:58 ` 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=8efaafd9-b01-c52f-4969-31628aa839a7@inria.fr \
--to=julia.lawall@inria.fr \
--cc=abrahamadekunle50@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®