From: Matthew Auld <matthew.auld@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, igt-dev@lists.freedesktop.org
Cc: chris.p.wilson@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t 3/3] i915/gem_exec_capture: fix needs_recoverable_ctx
Date: Thu, 7 Jul 2022 09:01:25 +0100 [thread overview]
Message-ID: <e08f6c1a-aa7e-8190-49c6-e1d4e40eb5fa@intel.com> (raw)
In-Reply-To: <20220706175912.6983-1-nirmoy.das@intel.com>
On 06/07/2022 18:59, Nirmoy Das wrote:
> needs_recoverable_ctx() should check for graphics_ver instead of
> display_ver. Use intel_graphics_ver() now that we have it.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/6356
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2022-07-07 8:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 12:01 [igt-dev] [PATCH i-g-t 1/2] lib/i915: Add graphics release subversion to device info Nirmoy Das
2022-07-06 12:01 ` [igt-dev] [PATCH i-g-t 2/2] i915/gem_exec_fence: Support dg2+ batch predication Nirmoy Das
2022-07-06 13:04 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] lib/i915: Add graphics release subversion to device info Patchwork
2022-07-06 17:59 ` [igt-dev] [PATCH i-g-t 3/3] i915/gem_exec_capture: fix needs_recoverable_ctx Nirmoy Das
2022-07-07 8:01 ` Matthew Auld [this message]
2022-07-06 18:38 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/2] lib/i915: Add graphics release subversion to device info Patchwork
2022-07-06 19:03 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-07-07 1:37 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-07 8:09 ` Das, Nirmoy
-- strict thread matches above, loose matches on Subject: below --
2022-07-06 18:00 [igt-dev] [PATCH i-g-t 1/3] " Nirmoy Das
2022-07-06 18:00 ` [igt-dev] [PATCH i-g-t 3/3] i915/gem_exec_capture: fix needs_recoverable_ctx Nirmoy Das
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=e08f6c1a-aa7e-8190-49c6-e1d4e40eb5fa@intel.com \
--to=matthew.auld@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=nirmoy.das@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.