linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 1/2] video: exynos: Remove OF dependency for Exynos DP
Date: Tue, 11 Feb 2014 14:27:33 +0000	[thread overview]
Message-ID: <52FA3355.80700@ti.com> (raw)
In-Reply-To: <1389933172-22991-1-git-send-email-sachin.kamat@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

On 11/02/14 14:01, Sachin Kamat wrote:
> On 10 February 2014 17:48, Tomi Valkeinen <tomi.valkeinen@ti.com> wrote:
>> On 17/01/14 06:32, Sachin Kamat wrote:
>>> Exynos is now a DT only platform. Hence there is no need
>>> for an explicit OF dependency. Remove it.
>>
>> But the driver still depends on OF, doesn't it? I don't think it's very
>> good for the driver Kconfig to make presumptions about what ARCH_*
>> depend on.
> 
> Depending upon nested dependencies is redundant IMHO.

Well, a driver should be independent of the underlying arch. In
practice, we have ARCH dependencies, as many of the devices only exist
on that arch. But I think the drivers should still be designed to be
arch-independent, as far as possible (omapdss compiles fine on x86).

If the driver depends on OF, it should depend on OF in the Kconfig, no
matter if the arch also depends on OF.

I don't really care if the EXYNOS_LCD_S6E8AX0 has OF dependency or not,
but to me this just looks unneeded cleanup, cluttering git logs, and in
my opinion it's even going to the wrong direction.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  parent reply	other threads:[~2014-02-11 14:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  4:44 [PATCH 1/2] video: exynos: Remove OF dependency for Exynos DP Sachin Kamat
2014-01-17  4:47 ` Jingoo Han
2014-01-17  4:58 ` Sachin Kamat
2014-01-17  5:12 ` Jingoo Han
2014-01-17  5:55 ` Sachin Kamat
2014-01-17  6:07 ` Jingoo Han
2014-01-17  9:03 ` Tomi Valkeinen
2014-01-17  9:33 ` Sachin Kamat
2014-01-21 10:56 ` Sachin Kamat
2014-02-10 12:18 ` Tomi Valkeinen
2014-02-11 12:13 ` Sachin Kamat
2014-02-11 14:27 ` Tomi Valkeinen [this message]
2014-02-12  7:20 ` Sachin Kamat
2014-02-12  7:25 ` Tomi Valkeinen
2014-02-12  8:41 ` Sachin Kamat

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=52FA3355.80700@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=linux-fbdev@vger.kernel.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).