From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>, fei.yang@intel.com
Cc: Jordan Justen <jordan.l.justen@intel.com>,
intel-gfx@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
dri-devel@lists.freedesktop.org,
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 12:56:29 +0100 [thread overview]
Message-ID: <37a0e8fc-efbc-973f-f163-235b9482f21c@linux.intel.com> (raw)
In-Reply-To: <ZGx7Quf+ArHnXOR0@ashyti-mobl2.lan>
On 23/05/2023 09:37, Andi Shyti wrote:
> Hi Fei,
>
> finally... pushed in drm-intel-gt-next! :)
I had to revert this (uapi commit only) by force pushing, luckily it was
the top commit.
1)
IGT is not merged yet.
2)
The tools/include/uapi/drm/i915_drm.h part of the patch was not removed.
Please fix both issues before re-sending and re-merging.
Regards,
Tvrtko
WARNING: multiple messages have this Message-ID (diff)
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>, fei.yang@intel.com
Cc: intel-gfx@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
dri-devel@lists.freedesktop.org,
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 12:56:29 +0100 [thread overview]
Message-ID: <37a0e8fc-efbc-973f-f163-235b9482f21c@linux.intel.com> (raw)
In-Reply-To: <ZGx7Quf+ArHnXOR0@ashyti-mobl2.lan>
On 23/05/2023 09:37, Andi Shyti wrote:
> Hi Fei,
>
> finally... pushed in drm-intel-gt-next! :)
I had to revert this (uapi commit only) by force pushing, luckily it was
the top commit.
1)
IGT is not merged yet.
2)
The tools/include/uapi/drm/i915_drm.h part of the patch was not removed.
Please fix both issues before re-sending and re-merging.
Regards,
Tvrtko
next prev parent reply other threads:[~2023-05-24 11:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 5:11 [PATCH v10 0/2] drm/i915: Allow user to set cache at BO creation fei.yang
2023-05-19 5:11 ` [Intel-gfx] " fei.yang
2023-05-19 5:11 ` [PATCH v10 1/2] drm/i915/mtl: end support for set caching ioctl fei.yang
2023-05-19 5:11 ` [Intel-gfx] " fei.yang
2023-05-19 5:11 ` [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation fei.yang
2023-05-19 5:11 ` [Intel-gfx] " fei.yang
2023-05-21 4:30 ` Jordan Justen
2023-05-21 4:30 ` [Intel-gfx] " Jordan Justen
2023-05-25 11:42 ` Extension detection by enumeration vs attempt to use extension (Was: Re: [Intel-gfx] [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation) Joonas Lahtinen
2023-05-25 11:42 ` [Intel-gfx] Extension detection by enumeration vs attempt to use extension (Was: " Joonas Lahtinen
2023-05-22 11:52 ` [PATCH v10 2/2] drm/i915: Allow user to set cache at BO creation Andi Shyti
2023-05-22 11:52 ` [Intel-gfx] " Andi Shyti
2023-05-22 15:25 ` Jordan Justen
2023-05-22 15:25 ` [Intel-gfx] " Jordan Justen
2023-05-22 15:30 ` Andi Shyti
2023-05-22 15:30 ` [Intel-gfx] " 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-23 8:37 ` Andi Shyti
2023-05-24 11:56 ` Tvrtko Ursulin [this message]
2023-05-24 11:56 ` Tvrtko Ursulin
2023-05-24 12:05 ` Tvrtko Ursulin
2023-05-24 12:05 ` Tvrtko Ursulin
2023-05-24 12:19 ` Andi Shyti
2023-05-24 12:19 ` Andi Shyti
2023-05-24 12:30 ` Andi Shyti
2023-05-24 12:30 ` Andi Shyti
2023-05-24 12:52 ` Tvrtko Ursulin
2023-05-24 12:52 ` Tvrtko Ursulin
2023-05-24 12:34 ` Tvrtko Ursulin
2023-05-24 12:34 ` Tvrtko Ursulin
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=37a0e8fc-efbc-973f-f163-235b9482f21c@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=fei.yang@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jordan.l.justen@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.