From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] More MERTOA WA's
Date: Mon, 11 May 2026 13:42:59 -0700 [thread overview]
Message-ID: <agI/U8qNKU6Qlo+I@soc-5CG1426VCC.clients.intel.com> (raw)
In-Reply-To: <20260430161459.2892545-1-ashutosh.dixit@intel.com>
Hi Ashutosh,
The WA states need to be updated. With that, the series is
Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Thanks,
Umesh
On Thu, Apr 30, 2026 at 09:14:55AM -0700, Ashutosh Dixit wrote:
>Ashutosh Dixit (4):
> drm/xe/oa: Refactor oa_unit_supports_oa_format
> drm/xe/oa: MERTOA Wa_14026746987
> drm/xe/oa: Add val arg to xe_oa_is_valid_config_reg
> drm/xe/oa: MERTOA Wa_14026779378
>
> drivers/gpu/drm/xe/regs/xe_oa_regs.h | 3 ++
> drivers/gpu/drm/xe/xe_device_wa_oob.rules | 2 ++
> drivers/gpu/drm/xe/xe_oa.c | 40 ++++++++++++++---------
> 3 files changed, 29 insertions(+), 16 deletions(-)
>
>--
>2.54.0
>
next prev parent reply other threads:[~2026-05-11 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 16:14 [PATCH 0/4] More MERTOA WA's Ashutosh Dixit
2026-04-30 16:14 ` [PATCH 1/4] drm/xe/oa: Refactor oa_unit_supports_oa_format Ashutosh Dixit
2026-04-30 16:14 ` [PATCH 2/4] drm/xe/oa: MERTOA Wa_14026746987 Ashutosh Dixit
2026-04-30 16:14 ` [PATCH 3/4] drm/xe/oa: Add val arg to xe_oa_is_valid_config_reg Ashutosh Dixit
2026-05-11 18:31 ` Umesh Nerlige Ramappa
2026-05-11 19:00 ` Dixit, Ashutosh
2026-05-11 20:41 ` Umesh Nerlige Ramappa
2026-04-30 16:14 ` [PATCH 4/4] drm/xe/oa: MERTOA Wa_14026779378 Ashutosh Dixit
2026-04-30 17:21 ` ✓ CI.KUnit: success for More MERTOA WA's Patchwork
2026-04-30 18:16 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-01 5:06 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-11 20:42 ` Umesh Nerlige Ramappa [this message]
2026-05-12 21:23 ` [PATCH 0/4] " Dixit, Ashutosh
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=agI/U8qNKU6Qlo+I@soc-5CG1426VCC.clients.intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).