public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Donald Hunter <donald.hunter@gmail•com>
To: Changwoo Min <changwoo@igalia•com>
Cc: lukasz.luba@arm•com,  rafael@kernel•org,  kuba@kernel•org,
	davem@davemloft•net,  edumazet@google•com,  pabeni@redhat•com,
	horms@kernel•org,  lenb@kernel•org,  pavel@kernel•org,
	kernel-dev@igalia•com,  linux-pm@vger•kernel.org,
	netdev@vger•kernel.org,  sched-ext@lists•linux.dev,
	linux-kernel@vger•kernel.org
Subject: Re: [PATCH for 6.19 2/4] PM: EM: Rename em.yaml to dev-energymodel.yaml
Date: Mon, 05 Jan 2026 11:25:09 +0000	[thread overview]
Message-ID: <m2344ki9nu.fsf@gmail.com> (raw)
In-Reply-To: <20251225040104.982704-3-changwoo@igalia.com>

Changwoo Min <changwoo@igalia•com> writes:

> The EM YNL specification used many acronyms, including ‘em’, ‘pd’,
> ‘ps’, etc. While the acronyms are short and convenient, they could be
> confusing. So, let’s spell them out to be more specific. The following
> changes were made in the spec. Note that the protocol name cannot exceed
> GENL_NAMSIZ (16).
>
>   em           -> dev-energymodel
>   pds          -> perf-domains
>   pd           -> perf-domain
>   pd-id        -> perf-domain-id
>   pd-table     -> perf-table
>   ps           -> perf-state
>   get-pds      -> get-perf-domains
>   get-pd-table -> get-perf-table
>   pd-created   -> perf-domain-created
>   pd-updated   -> perf-domain-updated
>   pd-deleted   -> perf-domain-deleted
>
> In addition. doc strings were added to the spec. based on the comments in
> energy_model.h. Two flag attributes (perf-state-flags and
> perf-domain-flags) were added for easily interpreting the bit flags.
>
> Finally, the autogenerated files and em_netlink.c were updated accordingly
> to reflect the name changes.
>
> Suggested-by: Donald Hunter <donald.hunter@gmail•com>
> Signed-off-by: Changwoo Min <changwoo@igalia•com>
> ---
>  .../netlink/specs/dev-energymodel.yaml        | 175 ++++++++++++++++++
>  Documentation/netlink/specs/em.yaml           | 116 ------------
>  MAINTAINERS                                   |   8 +-

YNL spec and MAINTAINERS

Reviewed-by: Donald Hunter <donald.hunter@gmail•com>

>  include/uapi/linux/dev_energymodel.h          |  89 +++++++++
>  include/uapi/linux/energy_model.h             |  63 -------
>  kernel/power/em_netlink.c                     | 135 ++++++++------
>  kernel/power/em_netlink_autogen.c             |  44 ++---
>  kernel/power/em_netlink_autogen.h             |  20 +-
>  8 files changed, 384 insertions(+), 266 deletions(-)
>  create mode 100644 Documentation/netlink/specs/dev-energymodel.yaml
>  delete mode 100644 Documentation/netlink/specs/em.yaml
>  create mode 100644 include/uapi/linux/dev_energymodel.h
>  delete mode 100644 include/uapi/linux/energy_model.h

  reply	other threads:[~2026-01-05 11:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-25  4:01 [PATCH for 6.19 0/4] Revise the EM YNL spec to be clearer Changwoo Min
2025-12-25  4:01 ` [PATCH for 6.19 1/4] PM: EM: Fix yamllint warnings in the EM YNL spec Changwoo Min
2025-12-31 17:20   ` Donald Hunter
2025-12-25  4:01 ` [PATCH for 6.19 2/4] PM: EM: Rename em.yaml to dev-energymodel.yaml Changwoo Min
2026-01-05 11:25   ` Donald Hunter [this message]
2025-12-25  4:01 ` [PATCH for 6.19 3/4] PM: EM: Change cpus' type from string to u64 array in the EM YNL spec Changwoo Min
2026-01-05 11:19   ` Donald Hunter
2025-12-25  4:01 ` [PATCH for 6.19 4/4] PM: EM: Add dump to get-perf-domains " Changwoo Min
2026-01-05 11:19   ` Donald Hunter
2026-01-06  8:25     ` Changwoo Min
2025-12-30  9:44 ` [PATCH for 6.19 0/4] Revise the EM YNL spec to be clearer Lukasz Luba
2025-12-30 12:56   ` Donald Hunter
2026-01-05 18:22   ` Rafael J. Wysocki
2026-01-07 11:52     ` Lukasz Luba

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=m2344ki9nu.fsf@gmail.com \
    --to=donald.hunter@gmail$(echo .)com \
    --cc=changwoo@igalia$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=kernel-dev@igalia$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=lenb@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-pm@vger$(echo .)kernel.org \
    --cc=lukasz.luba@arm$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=pavel@kernel$(echo .)org \
    --cc=rafael@kernel$(echo .)org \
    --cc=sched-ext@lists$(echo .)linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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