Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: "Chen, Angus" <angus.chen@intel.com>
Cc: andi.shyti@linux.intel.com, intel-gfx@lists.freedesktop.org,
	matthew.d.roper@intel.com, tejas.upadhyay@intel.com
Subject: Re: [PATCH v3] drm/i915/mtl: Update workaround 14018575942
Date: Tue, 11 Jun 2024 16:28:49 +0200	[thread overview]
Message-ID: <ZmhfIdm2DD8EJ8i2@ashyti-mobl2.lan> (raw)
In-Reply-To: <20240524173349.89123-1-angus.chen@intel.com>

Hi Angus,

On Fri, May 24, 2024 at 05:33:49PM +0000, Chen, Angus wrote:
> The WA should be extended to cover VDBOX engine. We found that
> 28-channels 1080p VP9 encoding may hit this issue.
> 
> v3: update the WA number and explain the reason why
>     this workaround is needed
> v2: add WA number
> v1: initial version
> 
> Signed-off-by: Chen, Angus <angus.chen@intel.com>

I had to do some manual work here, including the name/surname
reordring, because patchwork couldn't handle the --in-reply-to.

In any case, merged to drm-intel-gt-next.

Thanks,
Andi

      parent reply	other threads:[~2024-06-11 14:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  7:36 [PATCH] drm/i915/mtl: Update workaround 14018778641 Chen, Angus
2024-04-26  8:38 ` ✗ Fi.CI.BAT: failure for drm/i915/mtl: Update workaround 14018778641 (rev4) Patchwork
2024-04-29  9:53 ` [PATCH] drm/i915/mtl: Update workaround 14018778641 Andi Shyti
2024-04-30 11:20   ` Chen, Angus
2024-05-08 14:17     ` Upadhyay, Tejas
2024-05-13 13:29       ` [PATCH v2] " Chen, Angus
2024-05-14 13:11         ` Chen, Angus
2024-05-13 14:19       ` Chen, Angus
2024-05-23 22:31         ` Andi Shyti
2024-05-23 23:24           ` Matt Roper
2024-05-24 11:26             ` Andi Shyti
2024-05-24 16:00               ` Matt Roper
2024-05-24 17:33               ` [PATCH v3] drm/i915/mtl: Update workaround 14018575942 Chen, Angus
2024-05-27 10:38                 ` Andi Shyti
2024-06-11 14:28                 ` Andi Shyti [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=ZmhfIdm2DD8EJ8i2@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=angus.chen@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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