From: Nikolay Kulikov <nikolayof23@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dan Carpenter <error27@gmail.com>,
linux-staging@lists.linux.dev,
Nikolay Kulikov <nikolayof23@gmail.com>
Subject: [PATCH v2 0/4] staging: rtl8723bs: remove unused sys interrupt
Date: Tue, 12 May 2026 15:55:30 +0300 [thread overview]
Message-ID: <20260512125703.6878-1-nikolayof23@gmail.com> (raw)
This series removes fields 'SysIntrStatus' and 'SysIntrMask' from struct
hal_com_data.
'SysIntrStatus' is actually unused.
'SysIntrMask' is initialized to zero and never changes.
Changes in v2:
- update the commit message in patch 3
Nikolay Kulikov (4):
staging: rtl8723bs: remove unused SysIntrMask from struct hal_com_data
staging: rtl8723bs: remove empty InitSysInterrupt8723BSdio()
staging: rtl8723bs: remove overwriting of current IMR settings
staging: rtl8723bs: remove unused SysIntrStatus from struct
hal_com_data
drivers/staging/rtl8723bs/hal/sdio_halinit.c | 5 -----
drivers/staging/rtl8723bs/hal/sdio_ops.c | 20 --------------------
drivers/staging/rtl8723bs/include/hal_data.h | 4 ----
drivers/staging/rtl8723bs/include/sdio_ops.h | 1 -
4 files changed, 30 deletions(-)
base-commit: 6abf0b2df0b1c2205a4c0591425e6461afa62edb
--
2.54.0
next reply other threads:[~2026-05-12 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:55 Nikolay Kulikov [this message]
2026-05-12 12:55 ` [PATCH v2 1/4] staging: rtl8723bs: remove unused SysIntrMask from struct hal_com_data Nikolay Kulikov
2026-05-12 12:55 ` [PATCH v2 2/4] staging: rtl8723bs: remove empty InitSysInterrupt8723BSdio() Nikolay Kulikov
2026-05-12 12:55 ` [PATCH v2 3/4] staging: rtl8723bs: remove overwriting of current IMR settings Nikolay Kulikov
2026-05-12 12:55 ` [PATCH v2 4/4] staging: rtl8723bs: remove unused SysIntrStatus from struct hal_com_data Nikolay Kulikov
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=20260512125703.6878-1-nikolayof23@gmail.com \
--to=nikolayof23@gmail.com \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.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