From: Javier Martinez Canillas <javier.martinez@collabora.co.uk>
To: Kukjin Kim <kgene@kernel.org>, 'Kevin Hilman' <khilman@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
'Olof Johansson' <olof@lixom.net>
Subject: Re: exynos boot falures in linux-next
Date: Tue, 02 Dec 2014 09:32:16 +0100 [thread overview]
Message-ID: <547D7910.3020609@collabora.co.uk> (raw)
In-Reply-To: <00ae01d00465$10d9edb0$328dc910$@kernel.org>
Hello Kukjin,
On 11/20/2014 02:55 AM, Kukjin Kim wrote:
>>
> Yeah, it could be a best solution at this moment. Let me revert the commit
> 0ef76aea7a34 ("ARM: exynos_defconfig: Enable options for display panel
> support")
> from -next in samsung tree.
>
Maybe now that all the issues with the Exynos DRM driver that were causing
boot failures were found and fixed, we can enable these config options again?
After all, the fact that these symbols got enabled is what made the issues
to be detected in the first place so is useful to find regressions earlier.
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: exynos boot falures in linux-next
Date: Tue, 02 Dec 2014 09:32:16 +0100 [thread overview]
Message-ID: <547D7910.3020609@collabora.co.uk> (raw)
In-Reply-To: <00ae01d00465$10d9edb0$328dc910$@kernel.org>
Hello Kukjin,
On 11/20/2014 02:55 AM, Kukjin Kim wrote:
>>
> Yeah, it could be a best solution at this moment. Let me revert the commit
> 0ef76aea7a34 ("ARM: exynos_defconfig: Enable options for display panel
> support")
> from -next in samsung tree.
>
Maybe now that all the issues with the Exynos DRM driver that were causing
boot failures were found and fixed, we can enable these config options again?
After all, the fact that these symbols got enabled is what made the issues
to be detected in the first place so is useful to find regressions earlier.
Best regards,
Javier
next prev parent reply other threads:[~2014-12-02 8:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XqKYI-0000pQ-4b@ip-10-35-177-41.ec2.internal>
2014-11-17 15:57 ` exynos boot falures in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117)) Kevin Hilman
2014-11-17 16:57 ` exynos boot falures in linux-next Krzysztof Kozłowski
2014-11-17 16:57 ` Krzysztof Kozłowski
2014-11-17 22:24 ` Kevin Hilman
2014-11-17 22:24 ` Kevin Hilman
2014-11-17 23:25 ` Javier Martinez Canillas
2014-11-17 23:25 ` Javier Martinez Canillas
2014-11-18 2:30 ` Inki Dae
2014-11-18 2:30 ` Inki Dae
2014-11-18 3:49 ` Kevin Hilman
2014-11-18 3:49 ` Kevin Hilman
2014-11-19 17:01 ` Kevin Hilman
2014-11-19 17:01 ` Kevin Hilman
2014-11-19 17:06 ` Javier Martinez Canillas
2014-11-19 17:06 ` Javier Martinez Canillas
2014-11-20 1:55 ` Kukjin Kim
2014-11-20 1:55 ` Kukjin Kim
2014-12-02 8:32 ` Javier Martinez Canillas [this message]
2014-12-02 8:32 ` Javier Martinez Canillas
[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
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=547D7910.3020609@collabora.co.uk \
--to=javier.martinez@collabora.co.uk \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kgene@kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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.