From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Matthew Brost <matthew.brost@intel.com>
Subject: Re: [PATCH v2 2/4] drm/xe/guc: Introduce GUC_FIRMWARE_VER_AT_LEAST helper
Date: Mon, 15 Dec 2025 18:07:05 +0100 [thread overview]
Message-ID: <16d1dcde-cc15-49af-bbc8-6329de659f01@intel.com> (raw)
In-Reply-To: <20251215143739.196336-3-michal.wajdeczko@intel.com>
On 12/15/2025 3:37 PM, Michal Wajdeczko wrote:
> There are already few places in the code where we need to check GuC
> firmware version. Wrap existing raw conditions into a named helper
> macro to make it clear and avoid explicit call of the MAKE_GUC_VER.
>
> Suggested-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> ---
> v1: split from [1] (Michal)
> rename helper and add new macro (Daniele)
>
> [1] https://patchwork.freedesktop.org/patch/693953/?series=158874&rev=1
> ---
> note: there is yet another place that could be updated (xe_guc.c)
> but since it seems already broken (VFs don't know FW version)
> it should be fixed separately anyway.
posted [2] fix for this other usage
[2] https://patchwork.freedesktop.org/series/159040/#rev1
next prev parent reply other threads:[~2025-12-15 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 14:37 [PATCH v2 0/4] PF: Add handling for new adverse event thresholds Michal Wajdeczko
2025-12-15 14:37 ` [PATCH v2 1/4] drm/xe: Introduce IF_ARGS macro utility Michal Wajdeczko
2025-12-15 15:50 ` Michal Wajdeczko
2025-12-15 14:37 ` [PATCH v2 2/4] drm/xe/guc: Introduce GUC_FIRMWARE_VER_AT_LEAST helper Michal Wajdeczko
2025-12-15 17:07 ` Michal Wajdeczko [this message]
2025-12-15 18:25 ` Daniele Ceraolo Spurio
2025-12-15 14:37 ` [PATCH v2 3/4] drm/xe/pf: Prepare for new threshold KLVs Michal Wajdeczko
2025-12-15 18:28 ` Daniele Ceraolo Spurio
2025-12-15 14:37 ` [PATCH v2 4/4] drm/xe/pf: Add handling for MLRC adverse event threshold Michal Wajdeczko
2025-12-15 14:57 ` ✗ CI.checkpatch: warning for PF: Add handling for new adverse event thresholds (rev2) Patchwork
2025-12-15 14:59 ` ✓ CI.KUnit: success " Patchwork
2025-12-15 16:03 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-15 19:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-12-16 1:19 ` [PATCH v2 0/4] PF: Add handling for new adverse event thresholds Matthew Brost
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=16d1dcde-cc15-49af-bbc8-6329de659f01@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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