mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Erwan Velu <erwanaliasr1@gmail.com>
Cc: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>,
	 platform-driver-x86@vger.kernel.org,
	 Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>,
	 Carlos Bilbao <carlos.bilbao@kernel.org>,
	Hans de Goede <hansg@kernel.org>,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] platform/x86/amd/hsmp: Add /sys/devices/amd_hsmp socket devices
Date: Mon, 16 Nov 2026 16:57:23 +0200 (EET)	[thread overview]
Message-ID: <79f34929-c030-2f24-7663-5b18ff4d59dc@linux.intel.com> (raw)
In-Reply-To: <CAL2JzuyL63cqnV+DR22NfAPFHCO24G0_NkPohm1vao-U985pBw@mail.gmail.com>

On Mon, 16 Nov 2026, Erwan Velu wrote:

> > The lack of Documentation/ABI entry should not be taken as an indication
> > for something not being ABI. We generally don't take away ABI without
> > doing proper deprecation and waiting first.
> >
> > Sometimes, the old place can be covered with a symlink to the new place.
> 
> Yeah, but since the trees are very different between the current ACPI
> (AMDI) and the platform (socket<x>) one, I don't think a simple
> symlink would be accepted. Would it be ? That's my main issue here.
> The two implementations of the same structures vary so much that
> unifying the output means breaking one.
> The platform structure with socket<x>/ is way easier to manage from a
> monitoring software point of view.

If symlink is not possible, we just have to keep the old interface for the 
deprecation period then I think.

BTW, when submitting, you should also cc the AMD people who have been 
working with this driver recently (if they're not maintainers, tools fail 
to pick their names automatically).

-- 
 i.


  reply	other threads:[~2026-11-16 14:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-07 12:59 [PATCH 0/4] platform/x86/amd/hsmp: Unify per-socket sysfs metrics Erwan Velu
2026-10-07 12:59 ` [PATCH 1/4] platform/x86/amd/hsmp: Move per-socket sysfs attributes to common code Erwan Velu
2026-11-02  2:38   ` Carlos Bilbao
2026-10-07 12:59 ` [PATCH 2/4] platform/x86/amd/hsmp: Add /sys/devices/amd_hsmp socket devices Erwan Velu
2026-10-16 11:02   ` Ilpo Järvinen
2026-11-02  2:57   ` Carlos Bilbao
2026-11-16 14:11     ` Erwan Velu
2026-11-16 14:23       ` Ilpo Järvinen
2026-11-16 14:43         ` Erwan Velu
2026-11-16 14:57           ` Ilpo Järvinen [this message]
2026-10-07 12:59 ` [PATCH 3/4] platform/x86/amd/hsmp: Expose socket attributes from the platform driver Erwan Velu
2026-10-07 12:59 ` [PATCH 4/4] platform/x86/amd/hsmp: Add pwr_current_active_freq_limit_source_raw Erwan Velu
2026-11-02  2:41   ` Carlos Bilbao

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=79f34929-c030-2f24-7663-5b18ff4d59dc@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=carlos.bilbao.osdev@gmail.com \
    --cc=carlos.bilbao@kernel.org \
    --cc=erwanaliasr1@gmail.com \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=naveenkrishna.chatradhi@amd.com \
    --cc=platform-driver-x86@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

all inboxes | Powered by JetHome®