From: kbuild test robot <lkp@intel.com>
To: Dhananjay Kangude <dkangude@cadence.com>
Cc: kbuild-all@lists.01.org, linux-edac@vger.kernel.org
Subject: [RFC PATCH] EDAC/Cadence: data_synd[] can be static
Date: Wed, 26 Feb 2020 10:11:09 +0800 [thread overview]
Message-ID: <20200226021101.GA16779@e50d7db646c3> (raw)
In-Reply-To: <20200225093856.7328-2-dkangude@cadence.com>
Fixes: 201447a5db9b ("EDAC/Cadence:Add EDAC driver for cadence memory controller")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
cadence_edac.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/edac/cadence_edac.c b/drivers/edac/cadence_edac.c
index 3887db5665eee..17aa656a740ee 100644
--- a/drivers/edac/cadence_edac.c
+++ b/drivers/edac/cadence_edac.c
@@ -121,7 +121,7 @@
/* Syndrome values */
#define ECC_DOUBLE_MULTI_ERR_SYND 0x03
-char data_synd[] = {
+static char data_synd[] = {
0xf4, 0xf1, 0xec, 0xea, 0xe9, 0xe6, 0xe5, 0xe3,
0xdc, 0xda, 0xd9, 0xd6, 0xd5, 0xd3, 0xce, 0xcb,
0xb5, 0xb0, 0xad, 0xab, 0xa8, 0xa7, 0xa4, 0xa2,
@@ -132,7 +132,7 @@ char data_synd[] = {
0x1c, 0x1a, 0x19, 0x16, 0x15, 0x13, 0x0e, 0x0b
};
-char check_synd[] = {0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0x80};
+static char check_synd[] = {0x01, 0x02, 0x04, 0x08, 0x10, 0x20, 0x40, 0x80};
/**
* struct cdns_platform_data - cadence platform data structure.
next prev parent reply other threads:[~2020-02-26 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 9:38 [PATCH 0/2] Add EDAC support for Cadence ddr controller Dhananjay Kangude
2020-02-25 9:38 ` [PATCH 1/2] EDAC/Cadence:Add EDAC driver for cadence memory controller Dhananjay Kangude
2020-02-25 22:04 ` kbuild test robot
2020-02-26 2:11 ` kbuild test robot [this message]
2020-02-26 3:26 ` kbuild test robot
2020-02-25 9:38 ` [PATCH 2/2] dt-bindings: edac: Add cadence ddr mc support Dhananjay Kangude
2020-02-25 16:58 ` Rob Herring
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=20200226021101.GA16779@e50d7db646c3 \
--to=lkp@intel.com \
--cc=dkangude@cadence.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-edac@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;
as well as URLs for NNTP newsgroup(s).