From: shawn.guo@freescale.com (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] Fixes kernel Oops in imx-drm drivers
Date: Mon, 25 Aug 2014 19:48:24 +0800 [thread overview]
Message-ID: <1408967306-2624-1-git-send-email-shawn.guo@freescale.com> (raw)
In my testing of bind/unbind (and insmod/rmmod) on imx-drm drivers,
a couple of kernel Oops are seen. These two patches are trying to
fix them.
Changes since v1:
- Remove function ipu_plane_dpms() completely as suggested by Philipp
Shawn Guo (2):
imx-drm: imx-ldb: fix kernel Oops in imx_ldb_unbind()
imx-drm: ipuv3-plane: fix kernel Oops in ipu_dp_put()
drivers/staging/imx-drm/imx-ldb.c | 2 ++
drivers/staging/imx-drm/ipuv3-plane.c | 28 ++++------------------------
2 files changed, 6 insertions(+), 24 deletions(-)
--
1.9.1
next reply other threads:[~2014-08-25 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 11:48 Shawn Guo [this message]
2014-08-25 11:48 ` [PATCH v2 1/2] imx-drm: imx-ldb: fix kernel Oops in imx_ldb_unbind() Shawn Guo
2014-08-25 11:48 ` [PATCH v2 2/2] imx-drm: ipuv3-plane: fix kernel Oops in ipu_dp_put() Shawn Guo
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=1408967306-2624-1-git-send-email-shawn.guo@freescale.com \
--to=shawn.guo@freescale.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).