From: chenguohua@jari.cn
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] EDAC: Clean up errors in edac.h
Date: Fri, 13 Oct 2023 10:45:31 +0800 (GMT+08:00) [thread overview]
Message-ID: <631078e4.93f.18b26ecbdaf.Coremail.chenguohua@jari.cn> (raw)
Fix the following errors reported by checkpatch:
ERROR: "foo * bar" should be "foo *bar"
Signed-off-by: GuoHua Cheng <chenguohua@jari.cn>
---
include/linux/edac.h | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/edac.h b/include/linux/edac.h
index fa4bda2a70f6..c1f5a7ee8b6e 100644
--- a/include/linux/edac.h
+++ b/include/linux/edac.h
@@ -515,24 +515,24 @@ struct mem_ctl_info {
internal representation and configures whatever else needs
to be configured.
*/
- int (*set_sdram_scrub_rate) (struct mem_ctl_info * mci, u32 bw);
+ int (*set_sdram_scrub_rate) (struct mem_ctl_info *mci, u32 bw);
/* Get the current sdram memory scrub rate from the internal
representation and converts it to the closest matching
bandwidth in bytes/sec.
*/
- int (*get_sdram_scrub_rate) (struct mem_ctl_info * mci);
+ int (*get_sdram_scrub_rate) (struct mem_ctl_info *mci);
/* pointer to edac checking routine */
- void (*edac_check) (struct mem_ctl_info * mci);
+ void (*edac_check) (struct mem_ctl_info *mci);
/*
* Remaps memory pages: controller pages to physical pages.
* For most MC's, this will be NULL.
*/
/* FIXME - why not send the phys page to begin with? */
- unsigned long (*ctl_page_to_phys) (struct mem_ctl_info * mci,
+ unsigned long (*ctl_page_to_phys) (struct mem_ctl_info *mci,
unsigned long page);
int mc_idx;
struct csrow_info **csrows;
--
2.17.1
reply other threads:[~2023-10-13 2:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=631078e4.93f.18b26ecbdaf.Coremail.chenguohua@jari.cn \
--to=chenguohua@jari.cn \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).