public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: "Naik, Avadhut" <avadnaik@amd.com>
Cc: Avadhut Naik <avadhut.naik@amd.com>,
	linux-edac@vger.kernel.org, bp@alien8.de,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/5] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC interface
Date: Mon, 15 Sep 2025 13:04:20 -0400	[thread overview]
Message-ID: <20250915170420.GA850348@yaz-khff2.amd.com> (raw)
In-Reply-To: <ba326dbd-5216-4294-b645-c4ff2a2f6578@amd.com>

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

  reply	other threads:[~2025-09-15 17:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 18:53 [PATCH v3 0/5] Cleanup and add support for AMD Family 1Ah-based SOCs Avadhut Naik
2025-09-09 18:53 ` [PATCH v3 1/5] EDAC/amd64: Generate ctl_name string at runtime Avadhut Naik
2025-09-10 14:51   ` Yazen Ghannam
2025-09-10 15:53     ` Naik, Avadhut
2025-09-09 18:53 ` [PATCH v3 2/5] EDAC/amd64: Remove NUM_CONTROLLERS macro Avadhut Naik
2025-09-10 15:05   ` Yazen Ghannam
2025-09-10 15:48     ` Naik, Avadhut
2025-09-09 18:53 ` [PATCH v3 3/5] EDAC/amd64: Add support for AMD family 1Ah-based newer models Avadhut Naik
2025-09-10 15:13   ` Yazen Ghannam
2025-09-10 16:08     ` Naik, Avadhut
2025-09-09 18:53 ` [PATCH v3 4/5] EDAC/mc_sysfs: Increase legacy channel support to 16 Avadhut Naik
2025-09-10 15:17   ` Yazen Ghannam
2025-09-10 15:29     ` Naik, Avadhut
2025-09-09 18:53 ` [PATCH v3 5/5] EDAC/mc_sysfs: Begin deprecating legacy sysfs EDAC interface Avadhut Naik
2025-09-10 15:24   ` Yazen Ghannam
2025-09-10 17:38     ` Naik, Avadhut
2025-09-15 17:04       ` Yazen Ghannam [this message]
2025-09-16 16:09         ` 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=20250915170420.GA850348@yaz-khff2.amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=avadhut.naik@amd.com \
    --cc=avadnaik@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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