From: hanyu001@208suo.com
To: bp@alien8.de, tony.luck@intel.com, james.morse@arm.com,
mchehab@kernel.org, rric@kernel.org
Cc: linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] drivers: edac: add missing spaces after ','
Date: Fri, 14 Jul 2023 14:02:30 +0800 [thread overview]
Message-ID: <1793c783600cfd750100cfad8c47cfea@208suo.com> (raw)
In-Reply-To: <tencent_58287290BBAD4107FE7C2992CB229A625106@qq.com>
Fixes checkpatch.pl error
./drivers/edac/edac_device_sysfs.c:114: ERROR: space required after that
',' (ctx:VxV)
./drivers/edac/edac_device_sysfs.c:114: ERROR: space required after that
',' (ctx:VxV)
./drivers/edac/edac_device_sysfs.c:147: ERROR: space required after that
',' (ctx:VxV)
./drivers/edac/edac_device_sysfs.c:147: ERROR: space required after that
',' (ctx:VxV)
./drivers/edac/edac_device_sysfs.c:147: ERROR: space required after that
',' (ctx:VxV)
Signed-off-by: maqimei <2433033762@qq.com>
---
drivers/edac/edac_device_sysfs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/edac/edac_device_sysfs.c
b/drivers/edac/edac_device_sysfs.c
index 05d4353..f6d42bc 100644
--- a/drivers/edac/edac_device_sysfs.c
+++ b/drivers/edac/edac_device_sysfs.c
@@ -111,7 +111,7 @@ struct ctl_info_attribute {
};
#define to_ctl_info(k) container_of(k, struct edac_device_ctl_info,
kobj)
-#define to_ctl_info_attr(a) container_of(a,struct
ctl_info_attribute,attr)
+#define to_ctl_info_attr(a) container_of(a, struct ctl_info_attribute,
attr)
/* Function to 'show' fields from the edac_dev 'ctl_info' structure */
static ssize_t edac_dev_ctl_info_show(struct kobject *kobj,
@@ -144,7 +144,7 @@ static ssize_t edac_dev_ctl_info_store(struct
kobject *kobj,
.store = edac_dev_ctl_info_store
};
-#define CTL_INFO_ATTR(_name,_mode,_show,_store) \
+#define CTL_INFO_ATTR(_name, _mode, _show, _store) \
static struct ctl_info_attribute attr_ctl_info_##_name = { \
.attr = {.name = __stringify(_name), .mode = _mode }, \
.show = _show, \
next parent reply other threads:[~2023-07-14 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_58287290BBAD4107FE7C2992CB229A625106@qq.com>
2023-07-14 6:02 ` hanyu001 [this message]
[not found] <tencent_9292C0A2AD2275684250A6AD5447F83C1706@qq.com>
2023-07-14 3:53 ` hanyu001
[not found] <tencent_3DB677F4CD0F222D2C0E29A2858205A5D80A@qq.com>
2023-07-14 3:39 ` hanyu001
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=1793c783600cfd750100cfad8c47cfea@208suo.com \
--to=hanyu001@208suo.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=tony.luck@intel.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®