From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH v10 0/2] drm/i915: Allow user to set cache at BO creation
Date: Wed, 24 May 2023 13:34:30 +0100 [thread overview]
Message-ID: <648da5f9-48e0-7f28-7cd8-0f0bb1a0236a@linux.intel.com> (raw)
In-Reply-To: <ZG4Az4fWMsxL5j7w@ashyti-mobl2.lan>
On 24/05/2023 13:19, Andi Shyti wrote:
> Hi Tvrtko,
>
>>> finally... pushed in drm-intel-gt-next! :)
>>
>> I had to revert this (uapi commit only) by force pushing, luckily it was the
>> top commit.
>
> OK, sorry!
>
>> 1)
>> IGT is not merged yet.
>
> if igt is merged without the kernel it would fail, though.
Ideally it should skip, as with any new ABI testing. That way we can
nicely test the older kernels with the same IGT code base (like
drm-intel-fixes tree). So something like
igt_require(has_pat_ext_something) should be doable. Or just igt_skip if
most basic gem_create fails with the correct error code.
>
>> 2)
>> The tools/include/uapi/drm/i915_drm.h part of the patch was not removed.
>
> Will follow up on these two points.
Thank you!
Regards,
Tvrtko
prev parent reply other threads:[~2023-05-24 12:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 5:11 [Intel-gfx] [PATCH v10 0/2] drm/i915: Allow user to set cache at BO creation fei.yang
2023-05-19 5:11 ` [Intel-gfx] [PATCH v10 1/2] drm/i915/mtl: end support for set caching ioctl fei.yang
2023-05-19 5:11 ` [Intel-gfx] [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation fei.yang
2023-05-21 4:30 ` Jordan Justen
2023-05-25 11:42 ` [Intel-gfx] Extension detection by enumeration vs attempt to use extension (Was: Re: [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation) Joonas Lahtinen
2023-05-22 11:52 ` [Intel-gfx] [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation Andi Shyti
2023-05-22 15:25 ` Jordan Justen
2023-05-22 15:30 ` Andi Shyti
2023-05-19 5:53 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Allow user to set cache at BO creation (rev10) Patchwork
2023-05-19 6:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-19 10:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-23 8:37 ` [Intel-gfx] [PATCH v10 0/2] drm/i915: Allow user to set cache at BO creation Andi Shyti
2023-05-24 11:56 ` Tvrtko Ursulin
2023-05-24 12:05 ` Tvrtko Ursulin
2023-05-24 12:19 ` Andi Shyti
2023-05-24 12:30 ` Andi Shyti
2023-05-24 12:52 ` Tvrtko Ursulin
2023-05-24 12:34 ` Tvrtko Ursulin [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=648da5f9-48e0-7f28-7cd8-0f0bb1a0236a@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nirmoy.das@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