From: hanyu001@208suo.com
To: dlemoal@kernel.org
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] ata: space required after that ','
Date: Tue, 18 Jul 2023 17:48:22 +0800 [thread overview]
Message-ID: <a1b3139f2635446abf6f3c39306aa164@208suo.com> (raw)
In-Reply-To: <tencent_1D2A7704CC3721452CCE2B2E86EE04F5D90A@qq.com>
Fixes the following checkpatch errors:
./drivers/ata/libata-transport.c:92: ERROR: space required after that
',' (ctx:VxV)
./drivers/ata/libata-transport.c:92: ERROR: space required after that
',' (ctx:VxV)
./drivers/ata/libata-transport.c:92: ERROR: space required after that
',' (ctx:VxV)
./drivers/ata/libata-transport.c:92: ERROR: space required after that
',' (ctx:VxV)
./drivers/ata/libata-transport.c:94: ERROR: space required after that
',' (ctx:VxV)
./drivers/ata/libata-transport.c:94: ERROR: space required after that
',' (ctx:VxV)
./drivers/ata/libata-transport.c:94: ERROR: space required after that
',' (ctx:VxV)
Signed-off-by: Yu Han < hanyu001@208suo.com>
---
drivers/ata/libata-transport.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ata/libata-transport.c
b/drivers/ata/libata-transport.c
index e4fb9d1..4e87f77 100644
--- a/drivers/ata/libata-transport.c
+++ b/drivers/ata/libata-transport.c
@@ -89,9 +89,9 @@ struct ata_internal {
/*
* Hack to allow attributes of the same name in different objects.
*/
-#define ATA_DEVICE_ATTR(_prefix,_name,_mode,_show,_store) \
+#define ATA_DEVICE_ATTR(_prefix, _name, _mode, _show, _store) \
struct device_attribute device_attr_##_prefix##_##_name = \
- __ATTR(_name,_mode,_show,_store)
+ __ATTR(_name, _mode, _show, _store)
#define ata_bitfield_name_match(title, table) \
static ssize_t \
next parent reply other threads:[~2023-07-18 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_1D2A7704CC3721452CCE2B2E86EE04F5D90A@qq.com>
2023-07-18 9:48 ` hanyu001 [this message]
2023-07-18 10:49 ` Damien Le Moal
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=a1b3139f2635446abf6f3c39306aa164@208suo.com \
--to=hanyu001@208suo.com \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®