From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
To: Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
hansg@kernel.org, srinivas.pandruvada@linux.intel.com,
ilpo.jarvinen@linux.intel.com
Cc: linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>
Subject: Re: [PATCH v1 1/2] platform/x86/intel-uncore-freq: Rename instance_id
Date: Fri, 27 Mar 2026 19:56:58 +0200 [thread overview]
Message-ID: <91fdbcb6a8391cf945e53bccc3ae6f6f11412867.camel@linux.intel.com> (raw)
In-Reply-To: <3c02a8e3c1d4f07fa7f37740c33050c4e1d3f6ee.1774625521.git.m.wieczorretman@pm.me>
On Fri, 2026-03-27 at 15:36 +0000, Maciej Wieczor-Retman wrote:
> * @die_id: Die id for this instance
> * @domain_id: Power domain id for this instance
> * @cluster_id: cluster id in a domain
> - * @instance_id: Unique instance id to append to directory name
> + * @seqname_id: Unique id to append to directory name
> * @name: Sysfs entry name for this instance
> * @agent_type_mask: Bit mask of all hardware agents for this domain
> * @uncore_attr_group: Attribute group storage
> @@ -71,7 +71,7 @@ struct uncore_data {
> int die_id;
> int domain_id;
> int cluster_id;
> - int instance_id;
> + int seqname_id;
> char name[32];
> u16 agent_type_mask;
Nitpick: "seqname_id" reads like "sequence name ID" rather than a
sequence number. Consider "seqnum" or "sequence_id" for better clarity.
Just a suggestion based on how the name comes across, but not big deal.
Artem.
next prev parent reply other threads:[~2026-03-27 17:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 15:36 [PATCH v1 0/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs Maciej Wieczor-Retman
2026-03-27 15:36 ` [PATCH v1 1/2] platform/x86/intel-uncore-freq: Rename instance_id Maciej Wieczor-Retman
2026-03-27 17:56 ` Artem Bityutskiy [this message]
2026-03-27 21:06 ` Maciej Wieczor-Retman
2026-03-27 15:36 ` [PATCH v1 2/2] platform/x86/intel-uncore-freq: Expose instance ID in the sysfs Maciej Wieczor-Retman
2026-03-27 17:51 ` [PATCH v1 0/2] " Artem Bityutskiy
2026-03-27 21:03 ` Maciej Wieczor-Retman
2026-03-29 19:30 ` srinivas pandruvada
2026-03-30 8:11 ` Maciej Wieczor-Retman
2026-03-30 17:10 ` srinivas pandruvada
2026-03-30 17:52 ` Maciej Wieczor-Retman
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=91fdbcb6a8391cf945e53bccc3ae6f6f11412867.camel@linux.intel.com \
--to=artem.bityutskiy@linux.intel.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.wieczorretman@pm.me \
--cc=maciej.wieczor-retman@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
/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
Powered by JetHome