From: Philipp Zabel <p.zabel@pengutronix.de>
To: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, kernel@pengutronix.de
Subject: [GIT PULL] drm/imx: fixes for v5.12
Date: Thu, 1 Apr 2021 11:22:35 +0200 [thread overview]
Message-ID: <20210401092235.GA13586@pengutronix.de> (raw)
Hi Dave, Daniel,
this PR includes a regression fix for the imx-ldb driver, which fails to
register channel 1 if channel 0 is disabled since v5.12-rc2.
Also, there's an imx-ldb build warning fix for W=1 builds and a fix for
a memory leak in the imx-drm-core bind error path.
The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15:
Linux 5.12-rc2 (2021-03-05 17:33:41 -0800)
are available in the Git repository at:
git://git.pengutronix.de/git/pza/linux.git tags/imx-drm-fixes-2021-04-01
for you to fetch changes up to 33ce7f2f95cabb5834cf0906308a5cb6103976da:
drm/imx: imx-ldb: fix out of bounds array access warning (2021-03-25 07:48:34 +0100)
----------------------------------------------------------------
drm/imx: imx-drm-core and imx-ldb fixes
Fix a memory leak in an error path during DRM device initialization,
fix the LDB driver to register channel 1 even if channel 0 is unused,
and fix an out of bounds array access warning in the LDB driver.
----------------------------------------------------------------
Arnd Bergmann (1):
drm/imx: imx-ldb: fix out of bounds array access warning
Liu Ying (1):
drm/imx: imx-ldb: Register LDB channel1 when it is the only channel to be used
Pan Bian (1):
drm/imx: fix memory leak when fails to init
drivers/gpu/drm/imx/imx-drm-core.c | 2 +-
drivers/gpu/drm/imx/imx-ldb.c | 12 +++++++++++-
2 files changed, 12 insertions(+), 2 deletions(-)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2021-04-01 9:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210401092235.GA13586@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@pengutronix.de \
/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).