From: Luben Tuikov <luben.tuikov@amd.com>
To: Steven Price <steven.price@arm.com>,
dri-devel@lists.freedesktop.org, amd-gfx@lists.freedesktop.org
Cc: "Andrey Grodzovsky" <Andrey.Grodzovsky@amd.com>,
"kernel test robot" <lkp@intel.com>,
"Tomeu Vizoso" <tomeu.vizoso@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Alyssa Rosenzweig" <alyssa.rosenzweig@collabora.com>,
"Eric Anholt" <eric@anholt.net>,
"Christian Gmeiner" <christian.gmeiner@gmail.com>,
"Qiang Yu" <yuq825@gmail.com>,
"Russell King" <linux+etnaviv@armlinux.org.uk>,
"Alexander Deucher" <Alexander.Deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Lucas Stach" <l.stach@pengutronix.de>
Subject: Re: [PATCH 1/1] drm/scheduler: Job timeout handler returns status (v2)
Date: Fri, 11 Dec 2020 17:16:41 -0500 [thread overview]
Message-ID: <bb31086a-4d9e-f604-ea22-a2a2059d63c8@amd.com> (raw)
In-Reply-To: <19b4270f-2402-9381-b6e6-7ed508d4d996@amd.com>
On 2020-12-11 4:44 p.m., Luben Tuikov wrote:
> If however, you never decide to send it to the hardware and simply
> abandon it (in hopes that the DRM or the Application Client will
> reissue it), then you should send it back to DRM with status "COMPLETE".
Correction: "... decide to *not* send it to ..."
Regards,
Luben
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2020-12-11 22:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 2:14 [PATCH 0/1] Timeout handler now returns a value Luben Tuikov
2020-12-10 2:14 ` [PATCH 1/1] drm/scheduler: Job timeout handler returns status (v2) Luben Tuikov
2020-12-10 9:31 ` Lucas Stach
2020-12-10 9:41 ` Christian König
2020-12-11 20:44 ` Luben Tuikov
2020-12-14 9:00 ` Christian König
2020-12-11 20:36 ` Luben Tuikov
2020-12-17 15:53 ` Lucas Stach
2020-12-10 9:46 ` Steven Price
2020-12-11 21:44 ` Luben Tuikov
2020-12-11 22:16 ` Luben Tuikov [this message]
2020-12-14 9:00 ` Steven Price
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=bb31086a-4d9e-f604-ea22-a2a2059d63c8@amd.com \
--to=luben.tuikov@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=Andrey.Grodzovsky@amd.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.gmeiner@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=l.stach@pengutronix.de \
--cc=linux+etnaviv@armlinux.org.uk \
--cc=lkp@intel.com \
--cc=robh@kernel.org \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.com \
--cc=yuq825@gmail.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