From: Sasha Levin <sashal@kernel.org>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
stable@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dmitry.v.rogozhkin@intel.com,
Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Subject: Re: [PATCH] drm/i915: fix broadwell EU computation
Date: Thu, 29 Aug 2019 17:02:07 -0400 [thread overview]
Message-ID: <20190829210207.GM5281@sasha-vm> (raw)
In-Reply-To: <d7faaa1c-362f-ce9e-bbc9-adb5a7400b1f@intel.com>
On Thu, Aug 29, 2019 at 12:22:27AM +0300, Lionel Landwerlin wrote:
>On 29/08/2019 00:02, Rodrigo Vivi wrote:
>>From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>>
>>commit 6a67a20366f894c172734f28c5646bdbe48a46e3 upstream.
>>
>>subslice_mask is an array indexed by slice, not subslice.
>>
>>Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>>Fixes: 8cc7669355136f ("drm/i915: store all subslice masks")
>>Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108712
>>Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
>>Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>Link: https://patchwork.freedesktop.org/patch/msgid/20181112123931.2815-1-lionel.g.landwerlin@intel.com
>>(cherry picked from commit 63ac3328f0d1d37f286e397b14d9596ed09d7ca5)
>>Signed-off-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>>Cc: <stable@vger.kernel.org> # 4.17
>
>
>Rodrigo pointed out I forgot the Cc: tag which is why this didn't make
>it to stable.
>
>The same bug showed up on a CentOS kernel :
>https://github.com/intel/compute-runtime/issues/200
I just queued the upstream patch for 4.19, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-08-29 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 21:02 [PATCH] drm/i915: fix broadwell EU computation Rodrigo Vivi
2019-08-28 21:22 ` Lionel Landwerlin
2019-08-29 21:02 ` Sasha Levin [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=20190829210207.GM5281@sasha-vm \
--to=sashal@kernel.org \
--cc=chris@chris-wilson.co.uk \
--cc=dmitry.v.rogozhkin@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lionel.g.landwerlin@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--cc=tvrtko.ursulin@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