From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: "Kirill A . Shutemov" <kirill@shutemov.name>,
Carlos Santa <carlos.santa@intel.com>
Subject: Re: [PATCH 0/4] drm: Fix MST oopses in fbdev restore
Date: Wed, 26 Oct 2016 16:38:27 +0300 [thread overview]
Message-ID: <20161026133827.GG4617@intel.com> (raw)
In-Reply-To: <1477472755-15288-1-git-send-email-ville.syrjala@linux.intel.com>
On Wed, Oct 26, 2016 at 12:05:51PM +0300, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> This series would appear to be enough to avoid kernel oopses when trying
> to restore the fbdev setup after a MST device has been yanked.
>
> Apparently we still have some problems left in actually reacting properly
> to the changed situation, but at least the kernel no longer explodes.
>
> Entire series available here:
> git://github.com/vsyrjala/linux.git dp_mst_fixes_3
v2 patches available at:
git://github.com/vsyrjala/linux.git dp_mst_fixes_4
in case people want to re-test.
>
> Cc: Carlos Santa <carlos.santa@intel.com>
> Cc: Kirill A. Shutemov <kirill@shutemov.name>
>
> Ville Syrjälä (4):
> drm/fb-helper: Fix connector ref leak on error
> drm/fb-helper: Keep references for the current set of used connectors
> drm/dp/mst: Clear port->pdt when tearing down the i2c adapter
> drm/dp/mst: Check peer device type before attempting EDID read
>
> drivers/gpu/drm/drm_dp_mst_topology.c | 7 ++++++-
> drivers/gpu/drm/drm_fb_helper.c | 32 ++++++++++++++++++++++++--------
> 2 files changed, 30 insertions(+), 9 deletions(-)
>
> --
> 2.7.4
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-10-26 13:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 9:05 [PATCH 0/4] drm: Fix MST oopses in fbdev restore ville.syrjala
2016-10-26 9:05 ` [PATCH 1/4] drm/fb-helper: Fix connector ref leak on error ville.syrjala
2016-10-26 9:48 ` Chris Wilson
2016-10-26 9:05 ` [PATCH 2/4] drm/fb-helper: Keep references for the current set of used connectors ville.syrjala
2016-10-26 9:52 ` Chris Wilson
2016-10-26 12:34 ` Ville Syrjälä
2016-10-26 13:31 ` [PATCH v2 " ville.syrjala
2016-10-26 13:54 ` Chris Wilson
2016-10-26 14:11 ` Ville Syrjälä
2016-10-26 14:41 ` [PATCH v3 " ville.syrjala
2016-10-26 9:05 ` [PATCH 3/4] drm/dp/mst: Clear port->pdt when tearing down the i2c adapter ville.syrjala
2016-10-26 12:53 ` Daniel Vetter
2016-10-26 13:02 ` Ville Syrjälä
2016-10-26 13:30 ` [PATCH v2 " ville.syrjala
2016-10-26 13:35 ` Ville Syrjälä
2016-10-26 14:02 ` Daniel Vetter
2016-10-26 16:54 ` Daniel Vetter
2016-10-26 9:05 ` [PATCH 4/4] drm/dp/mst: Check peer device type before attempting EDID read ville.syrjala
2016-10-26 12:55 ` Daniel Vetter
2016-10-26 13:05 ` Ville Syrjälä
2016-10-26 18:31 ` Carlos Santa
2016-10-26 18:45 ` Ville Syrjälä
2016-10-26 13:38 ` Ville Syrjälä [this message]
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=20161026133827.GG4617@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=carlos.santa@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kirill@shutemov.name \
/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 NNTP newsgroup(s).