From: Matt Roper <matthew.d.roper@intel.com>
To: Xin Wang <x.wang@intel.com>
Cc: igt-dev@lists.freedesktop.org,
"Kamil Konieczny" <kamil.konieczny@linux.intel.com>,
"Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>,
"Ravi Kumar V" <ravi.kumar.vodapalli@intel.com>
Subject: Re: [PATCH v2 1/3] lib/intel: suffix PCI ID based gen/graphics_ver with _legacy
Date: Wed, 4 Feb 2026 10:30:03 -0800 [thread overview]
Message-ID: <20260204183003.GX458797@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20260122071530.1629046-2-x.wang@intel.com>
On Thu, Jan 22, 2026 at 07:15:28AM +0000, Xin Wang wrote:
> Rename the PCI ID translation helpers to intel_gen_legacy() and
> intel_graphics_ver_legacy() across callers.
> This is a preparatory step for introducing fd-based APIs.
Was this [mostly] generated in an automated manner via coccinelle or
sed? If so, it would be helpful to put the semantic patch or sed
command in the commit message so that the patch is easy for people to
re-generate (especially since the maintainers might want to re-generate
it right before applying if anything else landed in the meantime that
still uses the old names).
As a general note, I'd avoid using the suffix "legacy" since it's not
really clear what that means to someone who isn't reading these specific
mailing list threads. A more descriptive suffix like "_from_pciid"
might be a better choice.
>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Ravi Kumar V <ravi.kumar.vodapalli@intel.com>
> Signed-off-by: Xin Wang <x.wang@intel.com>
> ---
...snip...
>
> /**
> - * intel_gen:
> + * intel_gen_legacy:
> * @devid: pci device id
> *
> * Computes the Intel GFX generation for the given device id.
> @@ -747,12 +747,12 @@ const struct intel_cmds_info *intel_get_cmds_info(uint16_t devid)
> * Returns:
> * The GFX generation on successful lookup, -1u on failure.
I'd add some kind of disclaimer to the function documentation for these
indicating that this form is deprecated and should only be used in
places where there's no access to the device itself (e.g., DRM driver
isn't loaded, or a tool is being run in a different environment).
Matt
--
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation
next prev parent reply other threads:[~2026-02-04 18:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 7:15 [PATCH v2 0/3] lib/intel: switch graphics/IP version queries to fd-based APIs Xin Wang
2026-01-22 7:15 ` [PATCH v2 1/3] lib/intel: suffix PCI ID based gen/graphics_ver with _legacy Xin Wang
2026-02-04 18:30 ` Matt Roper [this message]
2026-01-22 7:15 ` [PATCH v2 2/3] lib/intel: add fd-based intel_gen/intel_graphics_ver via Xe query Xin Wang
2026-02-05 9:09 ` Jani Nikula
2026-01-22 7:15 ` [PATCH v2 3/3] intel/xe: use fd-based graphics/IP version helpers Xin Wang
2026-02-04 18:56 ` Matt Roper
2026-02-25 8:51 ` Wang, X
2026-02-25 23:18 ` Matt Roper
2026-01-22 8:01 ` ✓ i915.CI.BAT: success for lib/intel: switch graphics/IP version queries to fd-based APIs (rev2) Patchwork
2026-01-22 8:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-22 18:13 ` ✗ Xe.CI.Full: failure " Patchwork
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=20260204183003.GX458797@mdroper-desk1.amr.corp.intel.com \
--to=matthew.d.roper@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=ravi.kumar.vodapalli@intel.com \
--cc=x.wang@intel.com \
--cc=zbigniew.kempczynski@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