From: javier.martinez@collabora•co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists•infradead.org
Subject: exynos boot falures in linux-next
Date: Tue, 18 Nov 2014 00:25:10 +0100 [thread overview]
Message-ID: <546A83D6.9060504@collabora.co.uk> (raw)
In-Reply-To: <7hlhn9zcse.fsf@deeprootsystems.com>
Hello Kevin,
On 11/17/2014 11:24 PM, Kevin Hilman wrote:
>
> As might have been expected, reverting the change that enables the
> DRM/display options in exynos_defconfig fixes the problem.
>
> Kevin
>
I'm sorry for causing a boot failure but when I first posted that patch,
the Exynos DRM driver was working correctly (at least on the Exynos boards
I've access to) so it seems the regression was introduced while the patch
was posted but not yet picked.
I'm not sure what is the correct step in this case but I'm OK with
reverting the patch until the Exynos DRM driver bug is fixed.
Best regards,
Javier
next prev parent reply other threads:[~2014-11-17 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XqKYI-0000pQ-4b@ip-10-35-177-41.ec2.internal>
[not found] ` <7h61ed4xm3.fsf@deeprootsystems.com>
2014-11-17 18:21 ` mirabox boot fails in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117)) Thomas Petazzoni
[not found] ` <7hoas54y7k.fsf@deeprootsystems.com>
2014-11-17 16:57 ` exynos boot falures in linux-next Krzysztof Kozłowski
2014-11-17 22:24 ` Kevin Hilman
2014-11-17 23:25 ` Javier Martinez Canillas [this message]
2014-11-18 2:30 ` Inki Dae
2014-11-18 3:49 ` Kevin Hilman
2014-11-19 17:01 ` Kevin Hilman
2014-11-19 17:06 ` Javier Martinez Canillas
2014-11-20 1:55 ` Kukjin Kim
2014-12-02 8:32 ` Javier Martinez Canillas
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=546A83D6.9060504@collabora.co.uk \
--to=javier.martinez@collabora$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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