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 3/4] PM: EM: Change cpus' type from string to u64 array in the EM YNL spec
Date: Mon, 05 Jan 2026 11:19:37 +0000 [thread overview]
Message-ID: <m27btwi9x2.fsf@gmail.com> (raw)
In-Reply-To: <20251225040104.982704-4-changwoo@igalia.com>
Changwoo Min <changwoo@igalia•com> writes:
> Previously, the cpus attribute was a string format which was a "%*pb"
> stringification of a bitmap. That is not very consumable for a UAPI,
> so let’s change it to an u64 array of CPU ids.
>
> Suggested-by: Donald Hunter <donald.hunter@gmail•com>
> Signed-off-by: Changwoo Min <changwoo@igalia•com>
Reviewed-by: Donald Hunter <donald.hunter@gmail•com>
next prev parent 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
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 [this message]
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=m27btwi9x2.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