From: Andi Shyti <andi.shyti@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Jani Nikula <jani.nikula@intel.com>,
Intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>,
dri-devel@lists.freedesktop.org,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Matt Roper <matthew.d.roper@intel.com>
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915: Remove xehpsdv support
Date: Fri, 6 Oct 2023 15:30:13 +0200 [thread overview]
Message-ID: <ZSAL5VZ9BFMzDnQR@ashyti-mobl2.lan> (raw)
In-Reply-To: <20231006083103.660153-4-tvrtko.ursulin@linux.intel.com>
Hi Tvrtko,
On Fri, Oct 06, 2023 at 09:31:03AM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> XeHP SDV was a pre-production hardware used to bring up ATS and was not
> generally available. Since latter was since explicitly added, there is no
mmhh?
> need to keep the code for the former around.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
didn't spot anything odd... looks good:
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
next prev parent reply other threads:[~2023-10-06 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 8:31 [Intel-gfx] [PATCH 0/3] Trim some pre-production code Tvrtko Ursulin
2023-10-06 8:31 ` [Intel-gfx] [PATCH 1/3] drm/i915: Remove early/pre-production Haswell code Tvrtko Ursulin
2023-10-06 10:39 ` Andi Shyti
2023-10-06 10:46 ` Ville Syrjälä
2023-10-06 11:12 ` Tvrtko Ursulin
2023-10-06 15:44 ` Zanoni, Paulo R
2023-10-06 19:49 ` Andrzej Hajda
2023-10-06 8:31 ` [Intel-gfx] [PATCH 2/3] drm/i915: Remove incomplete PVC plumbing Tvrtko Ursulin
2023-10-06 12:06 ` Andi Shyti
2023-10-06 19:50 ` Andrzej Hajda
2023-10-06 8:31 ` [Intel-gfx] [PATCH 3/3] drm/i915: Remove xehpsdv support Tvrtko Ursulin
2023-10-06 13:30 ` Andi Shyti [this message]
2023-10-06 19:51 ` Andrzej Hajda
2023-10-06 9:05 ` [Intel-gfx] [PATCH 0/3] Trim some pre-production code Andi Shyti
2023-10-06 14:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2023-10-06 14:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-10-06 19:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Trim some pre-production code (rev2) Patchwork
2023-10-06 19:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-07 9:06 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=ZSAL5VZ9BFMzDnQR@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@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