From: Bert Karwatzki <spasswolf@web.de>
To: Jani Nikula <jani.nikula@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: "Matthew Brost" <matthew.brost@intel.com>,
"Luben Tuikov" <ltuikov89@gmail.com>,
"Danilo Krummrich" <dakr@redhat.com>,
"Christian König" <christian.koenig@amd.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@intel.com>
Subject: Re: drm scheduler redesign causes deadlocks [extended repost]
Date: Tue, 21 Nov 2023 10:45:15 +0100 [thread overview]
Message-ID: <3a0597d7ecd7778d43f3732b0adc408ca5e85e75.camel@web.de> (raw)
In-Reply-To: <87bkbno3z5.fsf@intel.com>
Am Dienstag, dem 21.11.2023 um 11:22 +0200 schrieb Jani Nikula:
> On Tue, 21 Nov 2023, Bert Karwatzki <spasswolf@web.de> wrote:
> > As this simple patch fixes the problem
>
> Please use git send-email to send patches. Evolution botched up the
> whitespace here.
>
> BR,
> Jani.
>
>
Noted (actually not the first time evolution has done this). But I'm not
resending the patches here because they are not meant as actual fixes, they only
serve to illustrate the problem, the cause of which is not known, yet.
Bert Karwatzki
next prev parent reply other threads:[~2023-11-21 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 9:00 drm scheduler redesign causes deadlocks [extended repost] Bert Karwatzki
2023-11-21 9:22 ` Jani Nikula
2023-11-21 9:45 ` Bert Karwatzki [this message]
2023-11-22 23:02 ` Luben Tuikov
2023-11-24 9:38 ` Bert Karwatzki
2023-11-25 20:03 ` Luben Tuikov
2023-11-27 16:09 ` [PATCH] drm/sched: Partial revert of "Qualify drm_sched_wakeup() by drm_sched_entity_is_ready()" Bert Karwatzki
2023-11-28 19:19 ` Luben Tuikov
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=3a0597d7ecd7778d43f3732b0adc408ca5e85e75.camel@web.de \
--to=spasswolf@web.de \
--cc=christian.koenig@amd.com \
--cc=dakr@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=ltuikov89@gmail.com \
--cc=matthew.brost@intel.com \
--cc=tvrtko.ursulin@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