From: Abraham Samuel Adekunle <abrahamadekunle50@gmail.com>
To: outreachy@lists.linux.dev, julia.lawall@inria.fr
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, andy@kernel.org,
Abraham Samuel Adekunle <abrahamadekunle50@gmail.com>
Subject: [PATCH v4 0/1] Unnecessary code cleanup patches
Date: Fri, 4 Apr 2025 09:50:20 +0100 [thread overview]
Message-ID: <cover.1743755621.git.abrahamadekunle50@gmail.com> (raw)
The patchset modifies unnecessary duplicate NULL tests on a value in an
expression, when the value has been NULL tested in a previous expression.
- Changes in v3:
- Changed other cases to use modulo (% 4096) over (& 0xfff).
- Modified commit message to reflect these changes.
- Changes in v2:
- Dropped patch files for media drivers from patchset as it is
not meant for outreachy applicants.
- Added full-stop sign to text in commit message.
- Made code more readable by adding a line break.
- Changed cases to use modulo (% 4096) over (& 0xff).
- Changes in v1
- Patch for drivers/staging/media/av7110/sp8870.c and
drivers/staging/media/atomisp/pci/atomisp_gmin_platform.c
is split into two different patches in the patchset for use by the different
driver maintainers.
- Added subject title for each of the separated patches.
- Patch 1: Removed unnecessary curly braces {} initially inserted.
- Patch 2: Unnecessary {} was also removed for v1.
Abraham Samuel Adekunle (1):
staging: rtl8723bs: Prevent duplicate NULL tests on a value
drivers/staging/rtl8723bs/core/rtw_mlme_ext.c | 2 +-
drivers/staging/rtl8723bs/core/rtw_xmit.c | 58 +++++++++----------
2 files changed, 30 insertions(+), 30 deletions(-)
--
2.34.1
next reply other threads:[~2025-04-04 8:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 8:50 Abraham Samuel Adekunle [this message]
2025-04-04 8:50 ` [PATCH v4 1/1] staging: rtl8723bs: Prevent duplicate NULL tests on a value Abraham Samuel Adekunle
2025-04-04 10:54 ` Andy Shevchenko
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=cover.1743755621.git.abrahamadekunle50@gmail.com \
--to=abrahamadekunle50@gmail.com \
--cc=andy@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--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 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.