From: Gustavo Padovan <gustavo@padovan.org>
To: Andrzej Hajda <a.hajda@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org, b.zolnierkie@samsung.com,
dri-devel@lists.freedesktop.org,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: [PATCH 3/3] drm/exynos: remove SoC checking code
Date: Tue, 9 Jun 2015 16:46:52 -0300 [thread overview]
Message-ID: <20150609194652.GB22853@joana> (raw)
In-Reply-To: <1433758542-9843-4-git-send-email-a.hajda@samsung.com>
Hi Andrzej,
2015-06-08 Andrzej Hajda <a.hajda@samsung.com>:
> SoC checking code is not necessary anymore, as exynos_drm_match_add and
> exynos_drm_platform_probe already properly handles situation when there are
> no Exynos DRM components.
>
> Signed-off-by: Andrzej Hajda <a.hajda@samsung.com>
> ---
> drivers/gpu/drm/exynos/exynos_drm_drv.c | 27 +--------------------------
> 1 file changed, 1 insertion(+), 26 deletions(-)
This series looks goods to me and works fine on my snow machine:
Tested-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Gustavo
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-06-09 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 10:15 [PATCH 0/3] exynos_drm initialization fix Andrzej Hajda
2015-06-08 10:15 ` [PATCH 1/3] drm/exynos: consolidate driver/device initialization code Andrzej Hajda
2015-06-11 14:33 ` Inki Dae
2015-06-08 10:15 ` [PATCH 2/3] drm/exynos: fix broken component binding in case of multiple pipelines Andrzej Hajda
2015-06-09 19:47 ` Gustavo Padovan
2015-06-10 7:49 ` [PATCH v2 " Andrzej Hajda
2015-06-08 10:15 ` [PATCH 3/3] drm/exynos: remove SoC checking code Andrzej Hajda
2015-06-09 19:46 ` Gustavo Padovan [this message]
2015-06-10 2:14 ` Hyungwon Hwang
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=20150609194652.GB22853@joana \
--to=gustavo@padovan.org \
--cc=a.hajda@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox