From: Jan Maslak <jan.maslak@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 2/2] lib/intel_device_info: Add missing flatccs flag for NVL-S
Date: Thu, 15 Jan 2026 15:03:36 +0100 [thread overview]
Message-ID: <aWjzuNoOvFYlvRsW@ART-DEV-395> (raw)
In-Reply-To: <20260115092155.114781-6-zbigniew.kempczynski@intel.com>
LGTM,
Reviewed-by: Jan Maslak <jan.maslak@intel.com>
On Thu, Jan 15, 2026 at 10:21:58AM +0100, Zbigniew Kempczyński wrote:
> Tests (render/blitter) which uses compressed buffer require flatccs
> flag defined in intel-device-info.
>
> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Jan Maślak <jan.maslak@intel.com>
> ---
> lib/intel_device_info.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/intel_device_info.c b/lib/intel_device_info.c
> index 20147479a8..89fa6788f5 100644
> --- a/lib/intel_device_info.c
> +++ b/lib/intel_device_info.c
> @@ -545,6 +545,7 @@ static const struct intel_device_info intel_novalake_s_info = {
> .display_ver = 35,
> .has_4tile = true,
> .has_oam = true,
> + .has_flatccs = true,
> .is_novalake_s = true,
> .codename = "novalake_s",
> .cmds_info = &xe2_cmds_info,
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-01-15 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 9:21 [PATCH i-g-t 0/2] Add missing flatccs flag for NVL-S Zbigniew Kempczyński
2026-01-15 9:21 ` [PATCH i-g-t 1/2] tests/xe_render_copy: Skip if platform doesn't support flatccs Zbigniew Kempczyński
2026-01-15 14:02 ` Jan Maslak
2026-01-15 9:21 ` [PATCH i-g-t 2/2] lib/intel_device_info: Add missing flatccs flag for NVL-S Zbigniew Kempczyński
2026-01-15 14:03 ` Jan Maslak [this message]
2026-01-15 10:05 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-01-15 10:23 ` ✓ i915.CI.BAT: " Patchwork
2026-01-15 11:15 ` ✓ Xe.CI.Full: " Patchwork
2026-01-15 12:29 ` ✗ i915.CI.Full: failure " Patchwork
2026-01-15 14:54 ` Zbigniew Kempczyński
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=aWjzuNoOvFYlvRsW@ART-DEV-395 \
--to=jan.maslak@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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