From: Danilo Krummrich <dakr@redhat.com>
To: Timur Tabi <ttabi@nvidia.com>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"kherbst@redhat.com" <kherbst@redhat.com>,
"lyude@redhat.com" <lyude@redhat.com>,
"airlied@gmail.com" <airlied@gmail.com>
Subject: Re: [PATCH 1/2] drm/nouveau: don't fini scheduler if not initialized
Date: Tue, 20 Feb 2024 20:56:40 +0100 [thread overview]
Message-ID: <948bb935-aa24-4bb0-ba1c-30d1da78023e@redhat.com> (raw)
In-Reply-To: <2ac14f50f2286f2b440e3a124eb1763e91d513de.camel@nvidia.com>
On 2/20/24 20:45, Timur Tabi wrote:
> On Mon, 2024-02-19 at 10:32 +0100, Danilo Krummrich wrote:
>>> Looks like I spoke too soon, I just hit the problem with the drm-next tree.
>>
>> Did you apply the patch to drm-next?
>
> Ugh, you're right. I don't how I got confused, but I could have sworn that I saw your two patches in drm-next, but they are not there.
>
> Sorry for the noise.
No worries, thanks for testing! :-)
next prev parent reply other threads:[~2024-02-20 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 0:05 [PATCH 1/2] drm/nouveau: don't fini scheduler if not initialized Danilo Krummrich
2024-02-02 0:05 ` [PATCH 2/2] drm/nouveau: omit to create schedulers using the legacy uAPI Danilo Krummrich
2024-02-02 17:14 ` [PATCH 1/2] drm/nouveau: don't fini scheduler if not initialized Timur Tabi
2024-02-02 17:24 ` Danilo Krummrich
2024-02-14 23:48 ` Timur Tabi
2024-02-19 9:32 ` Danilo Krummrich
2024-02-20 19:45 ` Timur Tabi
2024-02-20 19:56 ` Danilo Krummrich [this message]
2024-02-09 19:39 ` Dave Airlie
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=948bb935-aa24-4bb0-ba1c-30d1da78023e@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=ttabi@nvidia.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).