From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-xe@lists.freedesktop.org,
Bommu Krishnaiah <krishnaiah.bommu@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Tejas Upadhyay <tejas.upadhyay@intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Subject: Re: [PATCH v2] drm/xe/xe2: Add workaround 14021402888
Date: Wed, 8 May 2024 14:30:54 -0700 [thread overview]
Message-ID: <171520383041.475437.18119625215736341108.b4-ty@intel.com> (raw)
In-Reply-To: <20240418111534.481568-1-krishnaiah.bommu@intel.com>
On Thu, 18 Apr 2024 16:45:34 +0530, Bommu Krishnaiah wrote:
> This workaround applies to Graphics 20.01 as RCS engine workaround
>
>
Applied to drm-xe-next, thanks!
[1/1] drm/xe/xe2: Add workaround 14021402888
commit: 598dc939edf8d7bb1d69e84513c31451812128fc
Best regards,
--
Lucas De Marchi <lucas.demarchi@intel.com>
prev parent reply other threads:[~2024-05-08 21:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 11:15 [PATCH v2] drm/xe/xe2: Add workaround 14021402888 Bommu Krishnaiah
2024-04-18 11:38 ` ✓ CI.Patch_applied: success for drm/xe/xe2: Add workaround 14021402888 (rev2) Patchwork
2024-04-18 11:38 ` ✓ CI.checkpatch: " Patchwork
2024-04-18 11:39 ` ✓ CI.KUnit: " Patchwork
2024-04-18 12:01 ` ✓ CI.Build: " Patchwork
2024-04-18 12:03 ` ✓ CI.Hooks: " Patchwork
2024-04-18 12:05 ` ✓ CI.checksparse: " Patchwork
2024-04-18 12:19 ` [PATCH v2] drm/xe/xe2: Add workaround 14021402888 Ghimiray, Himal Prasad
2024-04-18 12:40 ` ✓ CI.BAT: success for drm/xe/xe2: Add workaround 14021402888 (rev2) Patchwork
2024-04-19 23:22 ` ✓ CI.FULL: " Patchwork
2024-04-30 14:42 ` [PATCH v2] drm/xe/xe2: Add workaround 14021402888 Lucas De Marchi
2024-05-03 9:29 ` Bommu, Krishnaiah
2024-05-08 21:30 ` Lucas De Marchi [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=171520383041.475437.18119625215736341108.b4-ty@intel.com \
--to=lucas.demarchi@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=krishnaiah.bommu@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=tejas.upadhyay@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).