From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
To: Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>,
Krzysztof Karas <krzysztof.karas@intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH i-g-t v2] tests/intel/gem_exec_params: add invalid-offset-multiple-buffers test
Date: Thu, 20 Aug 2026 10:26:58 +0200 [thread overview]
Message-ID: <DKTMMXD1PMXU.2TRC9WWVA6HPQ@intel.com> (raw)
In-Reply-To: <20260819152108.58688-2-krzysztof.niemiec@intel.com>
Hi Krzsztof,
On Wed Aug 19, 2026 at 5:21 PM CEST, Krzysztof Niemiec wrote:
> Add coverage for the case where the batch start offset is invalid with
> multiple BOs submitted, which was buggy in the kernel until 4fe2bd195435
> ("drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer")
>
> Signed-off-by: Krzysztof Niemiec <krzysztof.niemiec@intel.com>
> ---
Reviewed-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
--
Best regards,
Sebastian
prev parent reply other threads:[~2026-08-20 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 15:21 [PATCH i-g-t v2] tests/intel/gem_exec_params: add invalid-offset-multiple-buffers test Krzysztof Niemiec
2026-08-19 20:04 ` ✓ Xe.CI.BAT: success for tests/intel/gem_exec_params: add invalid-offset-multiple-buffers test (rev2) Patchwork
2026-08-19 20:45 ` ✓ i915.CI.BAT: " Patchwork
2026-08-20 0:14 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-08-20 2:36 ` ✗ i915.CI.Full: " Patchwork
2026-08-20 7:15 ` [PATCH i-g-t v2] tests/intel/gem_exec_params: add invalid-offset-multiple-buffers test Krzysztof Karas
2026-08-20 13:17 ` Krzysztof Niemiec
2026-08-20 8:26 ` Sebastian Brzezinka [this message]
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=DKTMMXD1PMXU.2TRC9WWVA6HPQ@intel.com \
--to=sebastian.brzezinka@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@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