From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
<dri-devel@lists.freedesktop.org>
Cc: Oded Gabbay <ogabbay@kernel.org>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Subject: Re: [PATCH v2 2/8] accel/ivpu: Cancel recovery work
Date: Thu, 23 Mar 2023 08:59:30 -0600 [thread overview]
Message-ID: <375f3dd4-eebb-e2bd-7fca-47d75ea6d5b9@quicinc.com> (raw)
In-Reply-To: <20230323125504.2586442-3-stanislaw.gruszka@linux.intel.com>
On 3/23/2023 6:54 AM, Stanislaw Gruszka wrote:
> Prevent running recovery_work after device is removed.
>
> Fixes: 852be13f3bd3 ("accel/ivpu: Add PM support")
> Signed-off-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Reviewed-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
next prev parent reply other threads:[~2023-03-23 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 12:54 [PATCH v2 0/8] accel/ivpu: Fixes for 6.3 Stanislaw Gruszka
2023-03-23 12:54 ` [PATCH v2 1/8] accel/ivpu: Do not access HW registers after unbind Stanislaw Gruszka
2023-03-23 12:54 ` [PATCH v2 2/8] accel/ivpu: Cancel recovery work Stanislaw Gruszka
2023-03-23 14:59 ` Jeffrey Hugo [this message]
2023-03-23 12:54 ` [PATCH v2 3/8] accel/ivpu: Do not use SSID 1 Stanislaw Gruszka
2023-03-23 15:00 ` Jeffrey Hugo
2023-03-23 12:55 ` [PATCH v2 4/8] accel/ivpu: Fix power down sequence Stanislaw Gruszka
2023-03-23 12:55 ` [PATCH v2 5/8] accel/ivpu: Disable buttress on device removal Stanislaw Gruszka
2023-03-23 12:55 ` [PATCH v2 6/8] accel/ivpu: Remove support for 1 tile SKUs Stanislaw Gruszka
2023-03-23 12:55 ` [PATCH v2 7/8] accel/ivpu: Fix VPU clock calculation Stanislaw Gruszka
2023-03-23 15:01 ` Jeffrey Hugo
2023-03-23 12:55 ` [PATCH v2 8/8] accel/ivpu: Fix IPC buffer header status field value Stanislaw Gruszka
2023-03-23 15:02 ` Jeffrey Hugo
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=375f3dd4-eebb-e2bd-7fca-47d75ea6d5b9@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=ogabbay@kernel.org \
--cc=stanislaw.gruszka@linux.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