From: Boris Petkov <bp@suse.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: alex_gagniuc@dellteam.com, austin_bolen@dell.com,
james.morse@arm.com, linux-edac@vger.kernel.org
Subject: Seen "Internal error: Can't find EDAC structure"?
Date: Fri, 20 Apr 2018 21:19:28 +0200 [thread overview]
Message-ID: <20180420191928.GS13977@pd.tnic> (raw)
On Fri, Apr 20, 2018 at 11:20:15AM -0700, Luck, Tony wrote:
> Ideas?
Does that help?
diff --git a/drivers/edac/ghes_edac.c b/drivers/edac/ghes_edac.c
index 68b6ee18bea6..4a9231993699 100644
--- a/drivers/edac/ghes_edac.c
+++ b/drivers/edac/ghes_edac.c
@@ -439,7 +439,7 @@ int ghes_edac_register(struct ghes *ghes, struct device *dev)
/* Check if safe to enable on this system */
idx = acpi_match_platform_list(plat_list);
if (!force_load && idx < 0)
- return 0;
+ return -ENODEV;
/*
* We have only one logical memory controller to which all DIMMs belong.
next reply other threads:[~2018-04-20 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 19:19 Boris Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-20 20:49 Seen "Internal error: Can't find EDAC structure"? Luck, Tony
2018-04-20 21:06 Boris Petkov
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=20180420191928.GS13977@pd.tnic \
--to=bp@suse.de \
--cc=alex_gagniuc@dellteam.com \
--cc=austin_bolen@dell.com \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.