From: Ahmet Sezgin Duran <ahmet@sezginduran.net>
To: gregkh@linuxfoundation.org
Cc: linux-fbdev@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Ahmet Sezgin Duran <ahmet@sezginduran.net>
Subject: [PATCH 0/4] staging: sm750fb: various code cleanups
Date: Tue, 12 May 2026 16:41:20 +0000 [thread overview]
Message-ID: <20260512164124.188210-1-ahmet@sezginduran.net> (raw)
This series performs several cleanups on the sm750fb staging driver to
improve code readability and remove redundancy.
The changes include:
- Removing unused header includes and blocks.
- Simplifying frequency validation logic using early returns to reduce
nesting.
- Removing a redundant variable initialization.
- Fixing a minor stylistic issue (double space).
All changes were verified to have no functional impact on the driver.
Ahmet Sezgin Duran (4):
staging: sm750fb: remove unused includes
staging: sm750fb: use early returns in frequency checks
staging: sm750fb: remove unnecessary initialization
staging: sm750fb: remove double space in assignment
drivers/staging/sm750fb/ddk750_chip.c | 153 +++++++++++++------------
drivers/staging/sm750fb/sm750.c | 12 --
drivers/staging/sm750fb/sm750_accel.c | 16 +--
drivers/staging/sm750fb/sm750_cursor.c | 15 ---
drivers/staging/sm750fb/sm750_hw.c | 17 ---
5 files changed, 79 insertions(+), 134 deletions(-)
base-commit: 6abf0b2df0b1c2205a4c0591425e6461afa62edb
--
2.53.0
next reply other threads:[~2026-05-12 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 16:41 Ahmet Sezgin Duran [this message]
2026-05-12 16:41 ` [PATCH 1/4] staging: sm750fb: remove unused includes Ahmet Sezgin Duran
2026-05-12 16:41 ` [PATCH 2/4] staging: sm750fb: use early returns in frequency checks Ahmet Sezgin Duran
2026-05-12 16:41 ` [PATCH 3/4] staging: sm750fb: remove unnecessary initialization Ahmet Sezgin Duran
2026-05-12 16:41 ` [PATCH 4/4] staging: sm750fb: remove double space in assignment Ahmet Sezgin Duran
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=20260512164124.188210-1-ahmet@sezginduran.net \
--to=ahmet@sezginduran.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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