From: Inki Dae <inki.dae@samsung.com>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
dri-devel@lists.freedesktop.org,
open list <linux-kernel@vger.kernel.org>,
"moderated list:ARM/S5P EXYNOS AR..."
<linux-samsung-soc@vger.kernel.org>
Subject: Re: [PATCH 0/9] drm/exynos: initialization/deinitialization fixes
Date: Wed, 17 Sep 2014 20:44:43 +0900 [thread overview]
Message-ID: <5419742B.4090907@samsung.com> (raw)
In-Reply-To: <1410268573-2297-1-git-send-email-a.hajda@samsung.com>
On 2014년 09월 09일 22:16, Andrzej Hajda wrote:
> This set of patches contains fixes of initialization and deinitialization
> code of exynos_drm core and components.
> It is based on exynos-drm-next branch.
>
> Patchset has been tested on trats and universal_c210 platforms.
Applied all patches except patch #5. As of now, it seems good to merge
also patch #5 if you couldn't post next version of that patch until the
end of this week. In this case, I will have a pull request including
that patch so that we can fix it up correctly later. Give me your
opinion if there is other plan.
Thanks,
Inki Dae
>
> Regards
> Andrzej
>
>
> Andrzej Hajda (9):
> drm/exynos/ipp: traverse ipp drivers list safely
> drm/exynos: fix drm driver de-initialization order
> drm/exynos/fbdev: fix fbdev gem object cleanup
> drm/exynos/fb: free exynos framebuffer on error
> drm/exynos/crtc: fix framebuffer reference sequence
> drm/exynos/dsi: unregister connector on removal
> drm/exynos/dpi: unregister connector and panel on removal
> drm/exynos/dp: unregister connector on removal
> drm/exynos/hdmi: unregister connector on removal
>
> drivers/gpu/drm/exynos/exynos_dp_core.c | 4 +++-
> drivers/gpu/drm/exynos/exynos_drm_crtc.c | 6 ++++++
> drivers/gpu/drm/exynos/exynos_drm_dpi.c | 6 +++++-
> drivers/gpu/drm/exynos/exynos_drm_drv.c | 8 ++++----
> drivers/gpu/drm/exynos/exynos_drm_dsi.c | 9 ++++++---
> drivers/gpu/drm/exynos/exynos_drm_fb.c | 1 +
> drivers/gpu/drm/exynos/exynos_drm_fbdev.c | 3 ---
> drivers/gpu/drm/exynos/exynos_drm_ipp.c | 4 ++--
> drivers/gpu/drm/exynos/exynos_hdmi.c | 4 +++-
> 9 files changed, 30 insertions(+), 15 deletions(-)
>
prev parent reply other threads:[~2014-09-17 11:44 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 13:16 [PATCH 0/9] drm/exynos: initialization/deinitialization fixes Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 1/9] drm/exynos/ipp: traverse ipp drivers list safely Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 2/9] drm/exynos: fix drm driver de-initialization order Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 3/9] drm/exynos/fbdev: fix fbdev gem object cleanup Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 4/9] drm/exynos/fb: free exynos framebuffer on error Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 5/9] drm/exynos/crtc: fix framebuffer reference sequence Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-12 8:34 ` Inki Dae
2014-09-12 8:34 ` Inki Dae
2014-09-12 8:57 ` Daniel Vetter
2014-09-12 8:57 ` Daniel Vetter
2014-09-12 9:21 ` Inki Dae
2014-09-12 9:21 ` Inki Dae
2014-09-12 9:27 ` Andrzej Hajda
2014-09-12 9:27 ` Andrzej Hajda
2014-09-12 10:45 ` Inki Dae
2014-09-12 11:04 ` Andrzej Hajda
2014-09-12 11:24 ` Inki Dae
2014-09-12 14:03 ` Daniel Vetter
2014-09-12 14:03 ` Daniel Vetter
2014-09-09 13:16 ` [PATCH 6/9] drm/exynos/dsi: unregister connector on removal Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 7/9] drm/exynos/dpi: unregister connector and panel " Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 8/9] drm/exynos/dp: unregister connector " Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-09 13:16 ` [PATCH 9/9] drm/exynos/hdmi: " Andrzej Hajda
2014-09-09 13:16 ` Andrzej Hajda
2014-09-17 11:44 ` Inki Dae [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=5419742B.4090907@samsung.com \
--to=inki.dae@samsung.com \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jy0922.shim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=sw0312.kim@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.