From: Borislav Petkov <bp@alien8.de>
To: "Ernst, Justin" <justin.ernst@hpe.com>,
"Luck, Tony" <tony.luck@intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"Anderson, Russ" <russ.anderson@hpe.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Aristeu Rozanski Filho <arozansk@redhat.com>
Subject: EDAC: Don't add devices under /sys/bus/edac
Date: Tue, 6 Nov 2018 15:45:35 +0100 [thread overview]
Message-ID: <20181106144535.GI13712@zn.tnic> (raw)
On Tue, Oct 02, 2018 at 06:26:08PM +0200, Borislav Petkov wrote:
> On Tue, Oct 02, 2018 at 03:51:41PM +0000, Ernst, Justin wrote:
> > The combined patches work on a 20 socket system.
> > Thanks!
>
> Cool, thanks for testing.
>
> Nevertheless, I'll queue them for 4.21 so that we have a full cycle of
> testing before we really kill the bus thing.
Ok, I've pushed the two patches ontop of EDAC's for-next branch, here:
https://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git/log/?h=edac-for-4.21-bus
and I'd appreciate testing them one more time on the big boxes you guys have.
Diffing sysfs here shows this:
which is the bus symlink:
subsystem -> ../../../../../../bus/mc0
and I think that's ok as nothing should be using it.
Thx.
--- edac.before 2018-11-06 13:37:37.925448609 +0100
+++ edac.after 2018-11-06 15:36:11.229497795 +0100
@@ -37,7 +37,6 @@
/sys/devices/system/edac/mc/mc0/dimm3/power/control
/sys/devices/system/edac/mc/mc0/dimm3/dimm_dev_type
/sys/devices/system/edac/mc/mc0/dimm3/size
-/sys/devices/system/edac/mc/mc0/dimm3/subsystem
/sys/devices/system/edac/mc/mc0/dimm3/dimm_ce_count
/sys/devices/system/edac/mc/mc0/dimm3/dimm_label
/sys/devices/system/edac/mc/mc0/dimm3/dimm_location
next reply other threads:[~2018-11-06 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 14:45 Borislav Petkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-13 19:15 EDAC: Don't add devices under /sys/bus/edac Borislav Petkov
2018-11-13 19:09 Justin Ernst
2018-10-02 16:26 Borislav Petkov
2018-10-02 15:51 Justin Ernst
2018-10-02 1:22 Mauro Carvalho Chehab
2018-10-01 22:43 Luck, Tony
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=20181106144535.GI13712@zn.tnic \
--to=bp@alien8.de \
--cc=arozansk@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=justin.ernst@hpe.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=russ.anderson@hpe.com \
--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