From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/7] drm/exynos: add super device support
Date: Sat, 5 Apr 2014 19:52:49 +0100 [thread overview]
Message-ID: <20140405185249.GM7528@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <53404BF3.2010409@gmail.com>
On Sat, Apr 05, 2014 at 08:31:15PM +0200, Tomasz Figa wrote:
> Maybe my words have been misinterpreted, but all I'm suggesting here is
> that there is no need to add any new data to DT to solve the same issue
> to the same extent as componentized subsystem framework, at least in
> Exynos case.
Right, so we seem to have agreement that what exynos is currently doing
is fundamentally broken.
So the next question is, how is it going to get fixed?
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-04-05 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1396355882-17010-1-git-send-email-inki.dae@samsung.com>
[not found] ` <1396355882-17010-2-git-send-email-inki.dae@samsung.com>
[not found] ` <533EB9C6.80302@samsung.com>
[not found] ` <CAAQKjZPbzb+qvJA5y+Kco9BRv4j3iVatM_0bd+ugyuVZUbfFFg@mail.gmail.com>
2014-04-05 17:32 ` [PATCH v2 1/7] drm/exynos: add super device support Tomasz Figa
2014-04-05 18:24 ` Russell King - ARM Linux
2014-04-05 18:31 ` Tomasz Figa
2014-04-05 18:52 ` Russell King - ARM Linux [this message]
2014-04-05 19:01 ` Tomasz Figa
2014-04-06 4:21 ` Inki Dae
2014-04-06 8:47 ` Russell King - ARM Linux
2014-04-06 9:38 ` Inki Dae
2014-04-06 3:15 ` Inki Dae
2014-04-07 14:18 ` Andrzej Hajda
2014-04-07 14:24 ` Tomasz Figa
2014-04-07 15:16 ` Inki Dae
2014-04-07 15:40 ` Tomasz Figa
2014-04-08 8:37 ` 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=20140405185249.GM7528@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).