Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>,
	Nirmoy Das <nirmoy.das@intel.com>
Cc: intel-gfx@lists.freedesktop.org, chris.p.wilson@linux.intel.com,
	andrzej.hajda@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Wait for active retire before i915_active_fini()
Date: Mon, 22 May 2023 19:35:14 +0200	[thread overview]
Message-ID: <ec8fbbf5-be0c-8d68-b4b6-78a2b76c95f9@linux.intel.com> (raw)
In-Reply-To: <ZGuCgYSm5Q/s8pzU@ashyti-mobl2.lan>

Hi Andi,

On 5/22/2023 4:56 PM, Andi Shyti wrote:
> Hi Nirmoy,
>
> On Mon, May 22, 2023 at 02:42:05PM +0200, Nirmoy Das wrote:
>> i915_active_fini() finalizes the debug object, which can occur before
>> the active retires and deactivates the debug object. Wait for one
>> final time before calling i915_active_fini();
>>
>> References: https://gitlab.freedesktop.org/drm/intel/-/issues/8311
>> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> does this need the Fixes: tag?


I can't pinpoint anything with a git blame also this is masked by

https://gitlab.freedesktop.org/drm/intel/-/issues/6733.

>
> Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>


Thanks,

Nirmoy

>
> Andi

  reply	other threads:[~2023-05-22 17:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 12:42 [Intel-gfx] [PATCH] drm/i915: Wait for active retire before i915_active_fini() Nirmoy Das
2023-05-22 14:47 ` Rodrigo Vivi
2023-05-22 14:56 ` Andi Shyti
2023-05-22 17:35   ` Das, Nirmoy [this message]
2023-05-22 15:23 ` Andrzej Hajda
2023-05-22 19:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-05-22 19:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-05-23  3:51 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-05-23 17:49 ` [Intel-gfx] [PATCH] " Das, Nirmoy

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=ec8fbbf5-be0c-8d68-b4b6-78a2b76c95f9@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=chris.p.wilson@linux.intel.com \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox