From: sunran001@208suo.com
To: hare@suse.com, jejb@linux.ibm.com, martin.petersen@oracle.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] scsi: aic79xx: fix some errors related to spaces
Date: Thu, 20 Jul 2023 17:22:07 +0800 [thread overview]
Message-ID: <3029a40608f9337530b3cb767d936f36@208suo.com> (raw)
In-Reply-To: <20230720092058.3618-1-xujianghui@cdjrlc.com>
ERROR: space prohibited before that close parenthesis ')'
ERROR: open brace '{' following struct go on the same line
ERROR: space prohibited before open square bracket '['
Signed-off-by: Ran Sun <sunran001@208suo.com>
---
drivers/scsi/aic7xxx/aic79xx.h | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/aic7xxx/aic79xx.h
b/drivers/scsi/aic7xxx/aic79xx.h
index 59e9321815c8..a1fdefdfddd8 100644
--- a/drivers/scsi/aic7xxx/aic79xx.h
+++ b/drivers/scsi/aic7xxx/aic79xx.h
@@ -66,7 +66,7 @@ struct scb_platform_data;
#define SCB_LIST_NULL 0xFF00
#define SCB_LIST_NULL_LE (ahd_htole16(SCB_LIST_NULL))
#define QOUTFIFO_ENTRY_VALID 0x80
-#define SCBID_IS_NULL(scbid) (((scbid) & 0xFF00 ) == SCB_LIST_NULL)
+#define SCBID_IS_NULL(scbid) (((scbid) & 0xFF00) == SCB_LIST_NULL)
#define SCSIID_TARGET(ahd, scsiid) \
(((scsiid) & TID) >> TID_SHIFT)
@@ -1043,8 +1043,7 @@ typedef enum {
typedef uint8_t ahd_mode_state;
-struct ahd_completion
-{
+struct ahd_completion {
uint16_t tag;
uint8_t sg_status;
uint8_t valid_tag;
@@ -1316,7 +1315,7 @@ struct aic7770_identity {
const char *name;
ahd_device_setup_t *setup;
};
-extern struct aic7770_identity aic7770_ident_table [];
+extern struct aic7770_identity aic7770_ident_table[];
extern const int ahd_num_aic7770_devs;
#define AHD_EISA_SLOT_OFFSET 0xc00
parent reply other threads:[~2023-07-20 9:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230720092058.3618-1-xujianghui@cdjrlc.com>]
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=3029a40608f9337530b3cb767d936f36@208suo.com \
--to=sunran001@208suo.com \
--cc=hare@suse.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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®