From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: "Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Christian Koenig <christian.koenig@amd.com>
Cc: airlied@gmail.com, Daniel Vetter <daniel.vetter@ffwll.ch>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
luben.tuikov@amd.com, Melissa Wen <mwen@igalia.com>,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>
Subject: Re: [PATCH v1] drm/scheduler: Fix lockup in drm_sched_entity_kill()
Date: Thu, 29 Dec 2022 13:15:06 +0300 [thread overview]
Message-ID: <41aecacc-44e5-1455-48cb-20e32187610c@collabora.com> (raw)
In-Reply-To: <3f87a88c-c375-4a02-0f09-4831544e5f96@igalia.com>
Hi,
On 12/27/22 22:28, Guilherme G. Piccoli wrote:
> Hi Dmitry / Christian, thanks for the fix!
>
> (And thanks Melissa for pointing that, saving me lots of time in
> research heh)
>
> Is this fix planned to be released on 6.2-rc cycle? I've just tested it
> on Steam Deck, and it resolved a lockup observed (since v6.2-rc1) -
> exactly the same thing mentioned in the commit message.
>
> FWIW:
> Tested-By: Guilherme G. Piccoli <gpiccoli@igalia.com> # Steam Deck
I'll push the patch to misc-fixes as soon as it will be rebased on
6.2-rc. Thanks!
Best regards,
Dmitry
next prev parent reply other threads:[~2022-12-29 10:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 0:13 Dmitry Osipenko
2022-11-23 6:40 ` Christian König
2022-11-23 13:22 ` Dmitry Osipenko
2022-12-27 19:28 ` Guilherme G. Piccoli
2022-12-29 10:15 ` Dmitry Osipenko [this message]
2022-12-29 18:52 ` Guilherme G. Piccoli
2023-01-02 15:01 ` Dmitry Osipenko
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=41aecacc-44e5-1455-48cb-20e32187610c@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gpiccoli@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luben.tuikov@amd.com \
--cc=mwen@igalia.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
all inboxes | Powered by JetHome®