From: Borislav Petkov <bp@alien8.de>
To: Qunqin Zhao <zhaoqunqin@loongson.cn>
Cc: Qunqin Zhao <zhaoqunqin@163.com>,
tony.luck@intel.com, linux-edac@vger.kernel.org,
chenhuacai@kernel.org, linux-kernel@vger.kernel.org,
Wang Jinwei <wangjinwei@loongson.cn>,
Yulong Wang <wangyulong@loongson.cn>,
Dongyan Qian <qiandongyan@loongson.cn>,
Chao Li <lichao@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>
Subject: Re: [PATCH v6 2/4] EDAC/loongson: Encode node and MC info into mc_idx
Date: Wed, 11 Nov 2026 08:08:26 +0000 [thread overview]
Message-ID: <88040256-91E2-4EAD-9571-4B460E69A93F@alien8.de> (raw)
In-Reply-To: <f34b681b-1499-43c8-b8a7-1437409bd709@loongson.cn>
On November 11, 2026 6:37:39 AM UTC, Qunqin Zhao <zhaoqunqin@loongson.cn> wrote:
>If we encode the presence of the _DSD property into mc_idx,
>
>the sysfs representation will become confusing. For example:
>
>loongson@loongson:~$ ls /sys/devices/system/edac/mc/
>mc65536 power subsystem uevent
>^^^^^^
Does it really matter which wrong numbers you have there? They are wrong no matter which ones you choose.
--
Small device. Typos and formatting crap
next prev parent reply other threads:[~2026-11-11 8:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 2:55 [PATCH v6 0/4] EDAC/loongson: Improvements for Loongson EDAC driver Qunqin Zhao
2026-11-05 2:55 ` [PATCH v6 1/4] EDAC/loongson: Rename driver-local symbols Qunqin Zhao
2026-11-05 7:10 ` Huacai Chen
2026-11-05 2:55 ` [PATCH v6 2/4] EDAC/loongson: Encode node and MC info into mc_idx Qunqin Zhao
2026-11-10 6:41 ` Borislav Petkov
2026-11-10 7:47 ` Qunqin Zhao
2026-11-10 8:03 ` Borislav Petkov
2026-11-10 8:23 ` Qunqin Zhao
2026-11-10 18:31 ` Borislav Petkov
2026-11-11 6:37 ` Qunqin Zhao
2026-11-11 8:08 ` Borislav Petkov [this message]
2026-11-11 8:33 ` Qunqin Zhao
2026-11-05 2:55 ` [PATCH v6 3/4] EDAC/loongson: Get DIMM size from ACPI _DSM method Qunqin Zhao
2026-11-05 2:55 ` [PATCH v6 4/4] EDAC/loongson: Add CS4-7 timeout filter for cross-node access Qunqin Zhao
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=88040256-91E2-4EAD-9571-4B460E69A93F@alien8.de \
--to=bp@alien8.de \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=lichao@loongson.cn \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiandongyan@loongson.cn \
--cc=tony.luck@intel.com \
--cc=wangjinwei@loongson.cn \
--cc=wangyulong@loongson.cn \
--cc=zhaoqunqin@163.com \
--cc=zhaoqunqin@loongson.cn \
/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®