From: Emil Velikov <emil.l.velikov@gmail.com>
To: Inki Dae <inki.dae@samsung.com>,
airlied@linux.ie, dri-devel@lists.freedesktop.org
Cc: "Matwey V. Kornilov" <matwey.kornilov@gmail.com>,
linux-samsung-soc@vger.kernel.org, emil.l.velikov@gmail.com
Subject: Re: [PATCH] drm/exynos: resolve infinite loop issue on non multi-platform
Date: Thu, 06 Nov 2014 15:46:47 +0000 [thread overview]
Message-ID: <545B97E7.2000004@gmail.com> (raw)
In-Reply-To: <545B976D.3000009@gmail.com>
On 06/11/14 15:44, Emil Velikov wrote:
> Hi Inki,
>
> With all respect,
>
> On 06/11/14 14:10, Inki Dae wrote:> This patch resovles the infinite
> loop issue incurred
>> when Exyno drm driver is enabled but all kms drivers
>> are disabled on Exynos board by returning -EPROBE_DEFER
>> only in case that there is kms device registered.
>>
> I believe it's preferred to add changelog, the original reporter (so
> that they can test) and the bug report in the commit message. Something
> like the following:
>
> v2:
> - Use drm_component_list the rather than of_machine_is_compatible to
> check for presence of an Exynos SoC.
>
> Cc: Matwey V. Kornilov <matwey.kornilov@gmail.com>
> References: https://bugzilla.kernel.org/show_bug.cgi?id=87691
>
I'm a genius. Please disregard the above.
-Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-11-06 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 14:10 [PATCH] drm/exynos: resolve infinite loop issue on non multi-platform Inki Dae
2014-11-06 15:44 ` Emil Velikov
2014-11-06 15:46 ` Emil Velikov [this message]
2014-11-06 17:08 ` Sjoerd Simons
2014-11-07 11:11 ` Andrzej Hajda
2014-11-07 16:27 ` Greg Kroah-Hartman
2014-11-07 8:29 ` Andrzej Hajda
2014-11-07 11:27 ` Inki Dae
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=545B97E7.2000004@gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=matwey.kornilov@gmail.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.