From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "tvrtko.ursulin@linux.intel.com" <tvrtko.ursulin@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v11 1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915
Date: Thu, 8 Dec 2022 17:04:47 +0000 [thread overview]
Message-ID: <4c1ce3ccee3fbb708fa71e008991f4ca0ed0f6fb.camel@intel.com> (raw)
In-Reply-To: <24e4cf79-4807-6097-028c-a0f915221f53@linux.intel.com>
On Thu, 2022-12-08 at 09:29 +0000, Tvrtko Ursulin wrote:
> Just some small comments and questions below.
>
> On 08/12/2022 05:01, Alan Previn wrote:
> > Starting with MTL, there will be two GT-tiles, a render and media
> >
Alan:[snip]
> IMO this looks great now - pretty self-documenting, all the complicated
> checks are contained to the init phase, and the comments are really good.
>
> Hopefully someone who knows the flows can cross-check this approach and
> r-b, Daniele I suspect (copied)? From me its an ack.
>
> Acked-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
Alan: Thanks Tvrtko. As per offline email, i created an internal JIRA to track the other follow ups (intel_pxp_foo(pxp) -> intel_pxp_foo(i915) and inlines that could use
CONFIG_I915_PXP - something that was there before but was removed for DG2 - perhaps could be added back in with accommodation on the internal functions).
I will rev v12 to fix the comments and Daniele has agreed to review the changes from v9 (prior RB point).
prev parent reply other threads:[~2022-12-08 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 5:01 [Intel-gfx] [PATCH v11 1/1] drm/i915/pxp: Promote pxp subsystem to top-level of i915 Alan Previn
2022-12-08 5:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v11,1/1] " Patchwork
2022-12-08 5:41 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-12-08 9:29 ` [Intel-gfx] [PATCH v11 1/1] " Tvrtko Ursulin
2022-12-08 17:04 ` Teres Alexis, Alan Previn [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=4c1ce3ccee3fbb708fa71e008991f4ca0ed0f6fb.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.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