From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Inki Dae <inki.dae@samsung.com>,
Joonyoung Shim <jy0922.shim@samsung.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
David Airlie <airlied@linux.ie>, Kukjin Kim <kgene@kernel.org>,
Jingoo Han <jg1.han@samsung.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Cc: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
Subject: Re: [RFT PATCH v2 0/3] drm/exynos: Fix build breakage on !DRM_EXYNOS_FIMD
Date: Thu, 07 May 2015 11:16:58 +0200 [thread overview]
Message-ID: <554B2D8A.6070209@collabora.co.uk> (raw)
In-Reply-To: <1430957086-25005-1-git-send-email-k.kozlowski@samsung.com>
Hello Krzysztof,
On 05/07/2015 02:04 AM, Krzysztof Kozlowski wrote:
> From: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
>
> Hi,
>
> This is second try to fix the build breakage introduced in 1c363c7cccf6
> ("drm/exynos: Enable DP clock to fix display on Exynos5250 and other").
>
> The fix is not trivial so I am kindly asking for testing on Chromebook
> and other DP-enabled boards (I don't have Chromebook right now).
>
For all the series:
Reviewed-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> Tested on Exynos4412 Trats2 board.
>
On Exynos5250 Snow, Exynos5420 Peach Pit and Exynos5800 Peach Pi Chromebooks:
Tested-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> Best regards,
> Krzysztof
>
Best regards,
Javier
WARNING: multiple messages have this Message-ID (diff)
From: javier.martinez@collabora.co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFT PATCH v2 0/3] drm/exynos: Fix build breakage on !DRM_EXYNOS_FIMD
Date: Thu, 07 May 2015 11:16:58 +0200 [thread overview]
Message-ID: <554B2D8A.6070209@collabora.co.uk> (raw)
In-Reply-To: <1430957086-25005-1-git-send-email-k.kozlowski@samsung.com>
Hello Krzysztof,
On 05/07/2015 02:04 AM, Krzysztof Kozlowski wrote:
> From: Krzysztof Kozlowski <k.kozlowski.k@gmail.com>
>
> Hi,
>
> This is second try to fix the build breakage introduced in 1c363c7cccf6
> ("drm/exynos: Enable DP clock to fix display on Exynos5250 and other").
>
> The fix is not trivial so I am kindly asking for testing on Chromebook
> and other DP-enabled boards (I don't have Chromebook right now).
>
For all the series:
Reviewed-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> Tested on Exynos4412 Trats2 board.
>
On Exynos5250 Snow, Exynos5420 Peach Pit and Exynos5800 Peach Pi Chromebooks:
Tested-by: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
> Best regards,
> Krzysztof
>
Best regards,
Javier
next prev parent reply other threads:[~2015-05-07 9:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 0:04 [RFT PATCH v2 0/3] drm/exynos: Fix build breakage on !DRM_EXYNOS_FIMD Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-07 0:04 ` [RFT PATCH v2 1/3] " Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-07 0:04 ` [RFT PATCH v2 2/3] drm/exynos: Constify exynos_drm_crtc_ops Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-11 13:29 ` Inki Dae
2015-05-11 13:29 ` Inki Dae
2015-05-11 13:29 ` Inki Dae
2015-05-07 0:04 ` [RFT PATCH v2 3/3] drm/exynos: Consolidate return statements in fimd_bind() Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-07 0:04 ` Krzysztof Kozlowski
2015-05-07 9:16 ` Javier Martinez Canillas [this message]
2015-05-07 9:16 ` [RFT PATCH v2 0/3] drm/exynos: Fix build breakage on !DRM_EXYNOS_FIMD Javier Martinez Canillas
2015-05-07 9:19 ` Krzysztof Kozlowski
2015-05-07 9:19 ` Krzysztof Kozlowski
2015-05-07 9:19 ` Krzysztof Kozlowski
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=554B2D8A.6070209@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=jg1.han@samsung.com \
--cc=jy0922.shim@samsung.com \
--cc=k.kozlowski.k@gmail.com \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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.