From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: tidy up and fix init-fail and teardown paths
Date: Wed, 16 Dec 2015 18:36:47 +0000 [thread overview]
Message-ID: <1450291011-31486-1-git-send-email-david.s.gordon@intel.com> (raw)
In-Reply-To: 1449845949-4161-1-git-send-email-nicholas.hoath@intel.com
A collection of small patches to fix some incorrect failure paths and
generally tidy up the corresponding teardown code, mostly relating to
contexts, and in particular the global default context that's created
at startup.
These should make subsequent reorganisation of other startup/teardown
code easier and safer.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-16 18:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 14:59 [PATCH v2] drm/i915: Fix context/engine cleanup order Nick Hoath
2015-12-11 16:26 ` Daniel Vetter
2015-12-11 18:58 ` Daniel Vetter
2015-12-16 18:36 ` Dave Gordon [this message]
2015-12-16 18:36 ` [PATCH 1/4] drm/i915: teardown default context in reverse, update comments Dave Gordon
2015-12-17 10:43 ` Nick Hoath
2015-12-21 10:48 ` Daniel Vetter
2015-12-21 11:01 ` Chris Wilson
2015-12-21 11:38 ` Dave Gordon
2015-12-16 18:36 ` [PATCH 2/4] drm/i915: mark the global default (intel_)context as such Dave Gordon
2015-12-16 18:57 ` Chris Wilson
2015-12-16 19:22 ` Dave Gordon
2015-12-16 19:30 ` Chris Wilson
2015-12-17 11:09 ` Nick Hoath
2015-12-17 12:27 ` Chris Wilson
2015-12-17 19:00 ` Dave Gordon
2015-12-18 16:02 ` Dave Gordon
2015-12-16 18:36 ` [PATCH 3/4] drm/i915: tidy up initialisation failure paths (legacy) Dave Gordon
2015-12-17 11:36 ` Nick Hoath
2015-12-16 18:36 ` [PATCH 4/4] drm/i915: tidy up initialisation failure paths (GEM & LRC) Dave Gordon
2015-12-17 11:37 ` Nick Hoath
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=1450291011-31486-1-git-send-email-david.s.gordon@intel.com \
--to=david.s.gordon@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.