From: Jeffy Chen <jeffy.chen@rock-chips.com>
To: linux-kernel@vger.kernel.org
Cc: briannorris@chromium.org, dianders@chromium.org,
tfiga@chromium.org, seanpaul@chromium.org, zyw@rock-chips.com,
marcheu@chromium.org, mark.yao@rock-chips.com, hshi@chromium.org,
Jeffy Chen <jeffy.chen@rock-chips.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
David Airlie <airlied@linux.ie>, Tom Gundersen <teg@jklm.no>,
Dave Airlie <airlied@redhat.com>
Subject: [PATCH v7 0/2] drm: rockchip: Fix rockchip drm unbind crash error
Date: Tue, 11 Apr 2017 11:31:40 +0800 [thread overview]
Message-ID: <1491881502-24357-1-git-send-email-jeffy.chen@rock-chips.com> (raw)
Verified on rk3399 chromebook kevin(with cros 4.4 kernel), no more crashes during unbind/bind drm.
Changes in v7:
Address Sean Paul <seanpaul@chromium.org>'s comments.
Update commit message.
Changes in v6:
Address Daniel Vetter <daniel@ffwll.ch>'s comments.
Changes in v5:
Fix wrong git account.
Changes in v2:
Fix some commit messages.
Jeffy Chen (2):
drm: Unplug drm device when unregistering it
drm: Prevent release fb after cleanup drm_mode_config
drivers/gpu/drm/drm_drv.c | 8 ++++----
drivers/gpu/drm/drm_framebuffer.c | 5 +++++
drivers/gpu/drm/udl/udl_drv.c | 2 +-
include/drm/drmP.h | 5 +++--
4 files changed, 13 insertions(+), 7 deletions(-)
--
2.1.4
next reply other threads:[~2017-04-11 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 3:31 Jeffy Chen [this message]
2017-04-11 3:31 ` [PATCH v7 1/2] drm: Unplug drm device when unregistering it Jeffy Chen
2017-04-12 6:33 ` Daniel Vetter
2017-04-12 8:17 ` jeffy
2017-04-12 8:44 ` jeffy
2017-04-11 3:31 ` [PATCH v7 2/2] drm: Prevent release fb after cleanup drm_mode_config Jeffy Chen
2017-04-12 6:36 ` Daniel Vetter
2017-04-12 8:39 ` jeffy
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=1491881502-24357-1-git-send-email-jeffy.chen@rock-chips.com \
--to=jeffy.chen@rock-chips.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=briannorris@chromium.org \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hshi@chromium.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcheu@chromium.org \
--cc=mark.yao@rock-chips.com \
--cc=seanpaul@chromium.org \
--cc=teg@jklm.no \
--cc=tfiga@chromium.org \
--cc=zyw@rock-chips.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;
as well as URLs for NNTP newsgroup(s).