dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: fei.yang@intel.com, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v15 0/1] drm/i915: Allow user to set cache at BO creation
Date: Mon, 5 Jun 2023 09:53:05 +0100	[thread overview]
Message-ID: <f7000b2e-e809-3801-48ba-d2a242dcb124@linux.intel.com> (raw)
In-Reply-To: <20230531171008.1738759-1-fei.yang@intel.com>


On 31/05/2023 18:10, fei.yang@intel.com wrote:
> From: Fei Yang <fei.yang@intel.com>
> 
> This series introduce a new extension for GEM_CREATE,
> 1. end support for set caching ioctl [PATCH 1/2]
> 2. add set_pat extension for gem_create [PATCH 2/2]
> 
> v2: drop one patch that was merged separately
>      commit 341ad0e8e254 ("drm/i915/mtl: Add PTE encode function")
> v3: rebased on https://patchwork.freedesktop.org/series/117082/
> v4: fix missing unlock introduced in v3, and
>      solve a rebase conflict
> v5: replace obj->cache_level with pat_set_by_user,
>      fix i915_cache_level_str() for legacy platforms.
> v6: rebased on https://patchwork.freedesktop.org/series/117480/
> v7: rebased on https://patchwork.freedesktop.org/series/117528/
> v8: dropped the two dependent patches that has been merged
>      separately. Add IGT link and Tested-by (MESA).
> v9: addressing comments (Andi)
> v10: acked-by and tested-by MESA
> v11: drop "end support for set caching ioctl" (merged)
>       remove tools/include/uapi/drm/i915_drm.h
> v12: drop Bspec reference in comment. add to commit message instead
> v13: sent to test with igt@gem_create@create-ext-set-pat
> v14: sent to test with igt@gem_create@create-ext-set-pat
> v15: update commit message with documentation note and t-b/a-b from
>       Media driver folks.
> 
> Fei Yang (1):
>    drm/i915: Allow user to set cache at BO creation
> 
>   drivers/gpu/drm/i915/gem/i915_gem_create.c | 36 +++++++++++++++++++
>   drivers/gpu/drm/i915/gem/i915_gem_object.c |  6 ++++
>   include/uapi/drm/i915_drm.h                | 41 ++++++++++++++++++++++
>   3 files changed, 83 insertions(+)
> 

Try with:

Test-with: 20230526172221.1438998-1-fei.yang@intel.com

That is how it is supposed to be done, to do a CI run against a test 
case not yet merged that is.

Regards,

Tvrtko

  parent reply	other threads:[~2023-06-05  8:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31 17:10 [PATCH v15 0/1] drm/i915: Allow user to set cache at BO creation fei.yang
2023-05-31 17:10 ` [PATCH v15 1/1] " fei.yang
2023-06-04 18:44   ` Andi Shyti
2023-06-05  2:52     ` Yang, Fei
2023-06-05  9:11   ` [Intel-gfx] " Tvrtko Ursulin
2023-06-05 16:47     ` Yang, Fei
2023-06-06  6:51       ` Yang, Fei
2023-06-06  7:57         ` Joonas Lahtinen
2023-06-05  8:53 ` Tvrtko Ursulin [this message]
2023-06-05  9:16   ` [Intel-gfx] [PATCH v15 0/1] " Tvrtko Ursulin
2023-06-05 15:04     ` Andi Shyti
2023-06-05 15:09     ` Yang, Fei

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=f7000b2e-e809-3801-48ba-d2a242dcb124@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fei.yang@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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