mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Avadhut Naik <avadhut.naik@amd.com>
To: <linux-edac@vger.kernel.org>, <linux-doc@vger.kernel.org>
Cc: <bp@alien8.de>, <gregkh@linuxfoundation.org>, <corbet@lwn.net>,
	<chenhuacai@kernel.org>, <mchehab+huawei@kernel.org>,
	<yazen.ghannam@amd.com>, <linux-kernel@vger.kernel.org>,
	<avadhut.naik@amd.com>
Subject: [PATCH v2 0/3] Cleanups in amd64_edac and removal of legacy EDAC sysfs interface
Date: Thu, 6 Nov 2025 01:54:43 +0000	[thread overview]
Message-ID: <20251106015727.1987246-1-avadhut.naik@amd.com> (raw)

This patchset undertakes some cleanups in the amd64_edac module and
removes the legacy EDAC sysfs interface since it has been obsolete for
more than a decade.

The first patch removes explicit assignment of the ctl_name string and
instead generates it at runtime using scnprintf.

The second patch removes the NUM_CONTROLLERS macro and instead uses the
max_mcs variable to determine the size of chipselect array.

The third patch removes the old EDAC sysfs interface.

NOTE:
These cleanups were earlier submitted as part of the set adding EDAC
support for AMD's newer Family 1Ah-based SOCs.[1] However, since the
support patches were critical to enabling EDAC on newer AMD SOCs and
since these cleanups were still under review, the set was split up.

[1]: https://lore.kernel.org/all/20250909185748.1621098-1-avadhut.naik@amd.com/

Changes in v2:
 - Drop the patch that set zn_regs_v2 flag for all SOCs based on Family
1Ah and later.
 - Change MAX_CTL_NAMELEN macro from 20 to 19.
 - Modify commit message of the second patch per feedback received.
 - Skip deprecation and just remove the old EDAC sysfs interface.

Links:
v1: https://lore.kernel.org/all/20251013173632.1449366-1-avadhut.naik@amd.com/

Avadhut Naik (3):
  EDAC/amd64: Generate ctl_name string at runtime
  EDAC/amd64: Remove NUM_CONTROLLERS macro
  edac: Remove the legacy EDAC sysfs interface

 Documentation/admin-guide/RAS/main.rst     | 142 +-------
 arch/loongarch/configs/loongson3_defconfig |   1 -
 drivers/edac/Kconfig                       |   8 -
 drivers/edac/amd64_edac.c                  |  61 +---
 drivers/edac/amd64_edac.h                  |   7 +-
 drivers/edac/edac_mc_sysfs.c               | 404 ---------------------
 6 files changed, 22 insertions(+), 601 deletions(-)


base-commit: d05ab93a9183520b2a6965765e14a3e6bdf01f90
-- 
2.43.0


             reply	other threads:[~2025-11-06  1:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06  1:54 Avadhut Naik [this message]
2025-11-06  1:54 ` [PATCH v2 1/3] EDAC/amd64: Generate ctl_name string at runtime Avadhut Naik
2025-11-06  1:54 ` [PATCH v2 2/3] EDAC/amd64: Remove NUM_CONTROLLERS macro Avadhut Naik
2025-11-06  1:54 ` [PATCH v2 3/3] edac: Remove the legacy EDAC sysfs interface Avadhut Naik
2025-11-07 12:40 ` [PATCH v2 0/3] Cleanups in amd64_edac and removal of " Borislav 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=20251106015727.1987246-1-avadhut.naik@amd.com \
    --to=avadhut.naik@amd.com \
    --cc=bp@alien8.de \
    --cc=chenhuacai@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=yazen.ghannam@amd.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

all inboxes | Powered by JetHome®