From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Avadhut Naik <avadhut.naik@amd.com>,
linux-edac@vger.kernel.org, yazen.ghannam@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC interface
Date: Fri, 31 Oct 2025 13:38:57 +0100 [thread overview]
Message-ID: <2025103150-subside-tux-fd46@gregkh> (raw)
In-Reply-To: <20251030191858.GEaQO6ImJ4fbqB_5ag@fat_crate.local>
On Thu, Oct 30, 2025 at 08:18:58PM +0100, Borislav Petkov wrote:
> On Thu, Oct 30, 2025 at 04:01:43PM +0100, Greg KH wrote:
> > No one is going to notice this type of kernel log message. If you think
> > that no one is using the sysfs files, delete them now. Why wait?
> >
> > sysfs is meant to be such that userspace can handle file removals (i.e.
> > that value is not present.) Unfortunately, sometimes this does not
> > actually happen and user tools do mess up and rely on things. So either
> > no one uses the file and it can be removed now, OR you have to leave it
> > in for "forever". There's no real chance to remove it later, that's
> > just postponing the decision.
>
> Lemme try to repeat what you're proposing to make sure we're on the same page:
>
> we simply zap the files and see if anyone complains. If yes, we figure out why
> they're using them and if they can't be moved to the new interface, we restore
> them and maintain them forever.
>
> Right?
Yup!
next prev parent reply other threads:[~2025-10-31 12:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 17:30 [PATCH 0/4] Cleanups in amd64_edac Avadhut Naik
2025-10-13 17:30 ` [PATCH 1/4] EDAC/amd64: Generate ctl_name string at runtime Avadhut Naik
2025-10-20 13:47 ` Borislav Petkov
2025-10-20 18:28 ` Naik, Avadhut
2025-10-20 19:09 ` Borislav Petkov
2025-10-13 17:30 ` [PATCH 2/4] EDAC/amd64: Remove NUM_CONTROLLERS macro Avadhut Naik
2025-10-21 10:44 ` Borislav Petkov
2025-10-22 6:07 ` Naik, Avadhut
2025-10-13 17:30 ` [PATCH 3/4] EDAC/amd64: Set zn_regs_v2 flag for all AMD Family 1Ah-based SOCs Avadhut Naik
2025-10-29 17:10 ` Borislav Petkov
2025-10-30 13:48 ` Yazen Ghannam
2025-11-03 21:18 ` Borislav Petkov
2025-11-04 14:59 ` Yazen Ghannam
2025-10-13 17:30 ` [PATCH 4/4] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC interface Avadhut Naik
2025-10-29 17:24 ` Borislav Petkov
2025-10-30 14:52 ` Naik, Avadhut
2025-10-30 15:01 ` Greg KH
2025-10-30 19:18 ` Borislav Petkov
2025-10-31 12:38 ` Greg KH [this message]
2025-10-31 12:54 ` Borislav Petkov
2025-10-31 19:34 ` Naik, Avadhut
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=2025103150-subside-tux-fd46@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=avadhut.naik@amd.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.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