From: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
To: Dmitry Osipenko <dmitry.osipenko@collabora.com>,
Erico Nunes <nunes.erico@gmail.com>,
Steven Price <steven.price@arm.com>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Rob Herring <robh@kernel.org>,
Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>,
Rob Clark <robdclark@gmail.com>,
Dmitry Osipenko <digetx@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v1] drm/scheduler: Don't kill jobs in interrupt context
Date: Wed, 6 Jul 2022 09:49:40 -0400 [thread overview]
Message-ID: <3e07a8d0-2cbc-8f3e-8f9f-5b73fb82028b@amd.com> (raw)
In-Reply-To: <107fe968-8311-0511-cc31-22feb994a6d7@collabora.com>
On 2022-07-06 03:07, Dmitry Osipenko wrote:
> Hello Andrey,
>
> On 5/17/22 17:48, Dmitry Osipenko wrote:
>> On 5/17/22 17:13, Andrey Grodzovsky wrote:
>>> Done.
>>>
>>> Andrey
>> Awesome, thank you!
>>
> Given that this drm-scheduler issue needs to be fixed in the 5.19-RC and
> earlier, shouldn't it be in the drm-fixes and not in drm-next?
I pushed it into drm-misc from where it got into drm-next. I don't have
permission for drm-fixes.
Andrey
>
next prev parent reply other threads:[~2022-07-06 13:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 22:15 Dmitry Osipenko
2022-04-12 16:51 ` Andrey Grodzovsky
2022-04-12 18:20 ` Dmitry Osipenko
2022-04-12 19:40 ` Andrey Grodzovsky
2022-04-12 19:55 ` Dmitry Osipenko
2022-04-12 22:59 ` Erico Nunes
2022-04-13 6:05 ` Dmitry Osipenko
2022-04-13 9:45 ` Erico Nunes
2022-04-13 10:04 ` Steven Price
2022-05-17 7:40 ` Erico Nunes
2022-05-17 9:03 ` Dmitry Osipenko
2022-05-17 14:03 ` Andrey Grodzovsky
2022-05-17 14:13 ` Andrey Grodzovsky
2022-05-17 14:48 ` Dmitry Osipenko
2022-07-06 7:07 ` Dmitry Osipenko
2022-07-06 13:49 ` Andrey Grodzovsky [this message]
2022-07-06 14:57 ` Dmitry Osipenko
2022-07-06 15:46 ` Alex Deucher
2022-07-12 8:56 ` Dmitry Osipenko
2022-07-14 9:57 ` Dmitry Osipenko
2022-07-14 14:14 ` Andrey Grodzovsky
2022-07-14 14:23 ` Dmitry Osipenko
2022-07-14 16:22 ` Alex Deucher
2022-07-14 17:58 ` Andrey Grodzovsky
2022-07-14 21:16 ` Alex Deucher
2022-07-15 15:18 ` Andrey Grodzovsky
2022-07-15 15:24 ` 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=3e07a8d0-2cbc-8f3e-8f9f-5b73fb82028b@amd.com \
--to=andrey.grodzovsky@amd.com \
--cc=airlied@linux.ie \
--cc=alyssa.rosenzweig@collabora.com \
--cc=daniel@ffwll.ch \
--cc=digetx@gmail.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nunes.erico@gmail.com \
--cc=robdclark@gmail.com \
--cc=robh@kernel.org \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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®