From: Lukas Wunner <lukas@wunner.de>
To: intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [PATCH v3 0/2] fbdev fixes
Date: Thu, 19 Nov 2015 14:00:59 +0100 [thread overview]
Message-ID: <cover.1447938059.git.lukas@wunner.de> (raw)
Respin of <cover.1446987413.git.lukas@wunner.de> with the following
changes as per feedback from Daniel and Ville:
- Order of the two patches is reversed.
- Patch 1 is rebased on Ville's async fbdev initialization changes.
- Patch 2 with reduced null pointer checks. (No need to check for
fb or obj, now that ifbdev is destroyed on initialization failure.)
Caution: I'm using current_is_async() in patch 1 to avoid a deadlock,
which is currently not exported. I've submitted a patch to export it
with <cover.1447937831.git.lukas@wunner.de>.
Should the patch be rejected, it's possible to solve it by spliting
intel_fbdev_fini() in two parts as suggested by Ville, however I think
using current_is_async() is preferrable as it's simpler and less code.
Browsable on GitHub:
https://github.com/l1k/linux/commits/intel_fbdev_fixes
Best regards,
Lukas
Lukas Wunner (2):
drm/i915: Tear down fbdev if initialization fails
drm/i915: Fix oops caused by fbdev initialization failure
drivers/gpu/drm/i915/i915_debugfs.c | 24 +++++++++++++-----------
drivers/gpu/drm/i915/intel_dp_mst.c | 10 ++++++++--
drivers/gpu/drm/i915/intel_fbdev.c | 16 +++++++++++-----
3 files changed, 32 insertions(+), 18 deletions(-)
--
2.1.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-11-19 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 13:00 Lukas Wunner [this message]
2015-11-18 12:43 ` [PATCH v3 2/2] drm/i915: Fix oops caused by fbdev initialization failure Lukas Wunner
2015-11-19 16:02 ` Daniel Vetter
2015-11-19 16:17 ` Lukas Wunner
2015-11-18 15:29 ` [PATCH v3 1/2] drm/i915: Tear down fbdev if initialization fails Lukas Wunner
2015-11-19 15:58 ` Daniel Vetter
2015-11-19 16:08 ` Lukas Wunner
2015-11-19 20:26 ` Lukas Wunner
2015-11-19 21:46 ` Chris Wilson
2015-11-19 22:25 ` Lukas Wunner
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=cover.1447938059.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=daniel.vetter@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox