From: Albab Hasan <albabhasan276@gmail.com>
To: linux-staging@lists.linux.dev
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
Albab Hasan <albabhasan276@gmail.com>
Subject: [PATCH] staging: vme_user: remove unimplemented #if 0 code blocks
Date: Sat, 28 Feb 2026 21:38:09 +0600 [thread overview]
Message-ID: <20260228153809.15398-1-albabhasan276@gmail.com> (raw)
Remove dead code in #if 0 blocks from struct vme_master
and struct vme_slave. these were never implemented or
compiled in.
checkpatch.pl reports:
WARNING: Consider removing the code enclosed by this #if 0 and its #endif
No functional changes.
Signed-off-by: Albab Hasan <albabhasan276@gmail.com>
---
drivers/staging/vme_user/vme_user.h | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/drivers/staging/vme_user/vme_user.h b/drivers/staging/vme_user/vme_user.h
index 19ecb05781cc..9e010974351d 100644
--- a/drivers/staging/vme_user/vme_user.h
+++ b/drivers/staging/vme_user/vme_user.h
@@ -14,11 +14,6 @@ struct vme_master {
__u32 aspace; /* Address Space */
__u32 cycle; /* Cycle properties */
__u32 dwidth; /* Maximum Data Width */
-#if 0
- char prefetchenable; /* Prefetch Read Enable State */
- int prefetchsize; /* Prefetch Read Size (Cache Lines) */
- char wrpostenable; /* Write Post State */
-#endif
} __packed;
/*
@@ -35,11 +30,6 @@ struct vme_slave {
__u64 size; /* Window Size */
__u32 aspace; /* Address Space */
__u32 cycle; /* Cycle properties */
-#if 0
- char wrpostenable; /* Write Post State */
- char rmwlock; /* Lock PCI during RMW Cycles */
- char data64bitcapable; /* non-VMEbus capable of 64-bit Data */
-#endif
} __packed;
struct vme_irq_id {
--
2.43.0
next reply other threads:[~2026-02-28 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 15:38 Albab Hasan [this message]
2026-03-01 19:25 ` [PATCH] staging: vme_user: remove unimplemented #if 0 code blocks Ethan Tidmore
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=20260228153809.15398-1-albabhasan276@gmail.com \
--to=albabhasan276@gmail.com \
--cc=gregkh@linuxfoundation.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