linux-kernel - Re: [PATCH v3 5/5] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250915170420.GA850348@yaz-khff2.amd.com>
Date: Mon, 15 Sep 2025 13:04:20 -0400
From: Yazen Ghannam <yazen.ghannam@....com>
To: "Naik, Avadhut" <avadnaik@....com>
Cc: Avadhut Naik <avadhut.naik@....com>, linux-edac@...r.kernel.org,
	bp@...en8.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 5/5] EDAC/mc_sysfs: Begin deprecating legacy sysfs
 EDAC interface

On Wed, Sep 10, 2025 at 12:38:44PM -0500, Naik, Avadhut wrote:

[...]
> > And maybe the warning can go in an short inline function? Sorry, I
> > forgot if this came up already.
> > 
> > Also, "two future releases" is vague. And it may be confusing if this is
> > backported.
> >
> > Does anyone have a better suggestion, or is this good as-is?
> >
> 
> How about explicitly stating a release?
> 6.20, for example.
>  

I think that may be okay, but I'm not sure.

Boris, what do you think?

Thanks,
Yazen