linux-kernel - [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: <b33562a9-e143-485d-b1cc-94a79a2cf6a9@amd.com>
Date: Tue, 16 Sep 2025 11:09:55 -0500
From: "Naik, Avadhut" <avadnaik@....com>
To: Yazen Ghannam <yazen.ghannam@....com>
Cc: Avadhut Naik <avadhut.naik@....com>, linux-edac@...r.kernel.org,
 bp@...en8.de, linux-kernel@...r.kernel.org
Subject: [PATCH v3 5/5] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC
 interface



On 9/15/2025 12:04, Yazen Ghannam wrote:
> 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

Another alternative could be doing something like this:

[ 1340.644001] NOTICE: Automounting of tracing to debugfs is deprecated and will be removed in 2030

Mention the year instead of release!

-- 
Thanks,
Avadhut Naik