From: Jani Nikula <jani.nikula@intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: "Michał Grzelak" <michal.grzelak@intel.com>
Subject: Re: [PATCH v1 0/1] rename GEN6_PCODE_DATA to match spec
Date: Fri, 23 Jan 2026 13:42:50 +0200 [thread overview]
Message-ID: <74be2b0358f824af7aa7ddcbf15aed3e8424b1a0@intel.com> (raw)
In-Reply-To: <20260123105525.572035-1-michal.grzelak@intel.com>
On Fri, 23 Jan 2026, Michał Grzelak <michal.grzelak@intel.com> wrote:
> This patch should be applied on top of [1].
>
> [1]
> https://lore.kernel.org/intel-gfx/20260115113337.4079184-1-jani.nikula@intel.com
There's not a whole lot of point in sending patches that depend on other
patches, because you won't get CI results, and any review depends on the
other patch having been merged.
BR,
Jani.
>
> BR,
> Michał
>
> Michał Grzelak (1):
> drm/{i915,xe}/pcode: rename GEN6_PCODE_DATA to match spec
>
> drivers/gpu/drm/i915/display/intel_parent.c | 4 ++--
> drivers/gpu/drm/i915/display/intel_parent.h | 2 +-
> drivers/gpu/drm/i915/gvt/handlers.c | 2 +-
> drivers/gpu/drm/i915/i915_reg.h | 2 +-
> drivers/gpu/drm/i915/intel_gvt_mmio_table.c | 2 +-
> drivers/gpu/drm/i915/intel_pcode.c | 14 +++++++-------
> drivers/gpu/drm/i915/intel_pcode.h | 2 +-
> drivers/gpu/drm/xe/display/xe_display_pcode.c | 4 ++--
> drivers/gpu/drm/xe/xe_pcode.c | 4 ++--
> drivers/gpu/drm/xe/xe_pcode.h | 2 +-
> 10 files changed, 19 insertions(+), 19 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-01-23 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 10:55 [PATCH v1 0/1] rename GEN6_PCODE_DATA to match spec Michał Grzelak
2026-01-23 10:55 ` [PATCH 1/1] drm/{i915, xe}/pcode: " Michał Grzelak
2026-01-23 11:42 ` Jani Nikula [this message]
2026-01-23 11:44 ` ✗ Fi.CI.BUILD: failure for " 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=74be2b0358f824af7aa7ddcbf15aed3e8424b1a0@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.grzelak@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