From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] video: omap2: Compile omap2 support only when
Date: Mon, 20 Jun 2011 13:06:41 +0000 [thread overview]
Message-ID: <1308575201.2076.57.camel@deskari> (raw)
In-Reply-To: <1308566761-2850-3-git-send-email-tushar.behera@linaro.org>
On Mon, 2011-06-20 at 16:16 +0530, Tushar Behera wrote:
> Currently display support for omap2 is selected by default and
> it gets built for all the configurations.
>
> Instead of it being a built-in feature, it's compilation should
> depend on the config option CONFIG_FB_OMAP2.
No, I don't think so. omap2 directory contains vram, vrfb and omapdss,
all of which can be used without omapfb driver. vram and vrfb can be
even used without omapdss driver.
Is this patch fixing some real problem?
Tomi
next prev parent reply other threads:[~2011-06-20 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 10:57 [PATCH 0/2] video: Make omap2 support conditional Tushar Behera
2011-06-20 10:58 ` [PATCH 1/2] config: omap2+: force fb and dss support as built-in Tushar Behera
2011-06-20 12:19 ` Premi, Sanjeev
2011-06-20 12:20 ` [PATCH 1/2] config: omap2+: force fb and dss support as Russell King - ARM Linux
2011-06-20 12:36 ` [PATCH 1/2] config: omap2+: force fb and dss support as built-in Premi, Sanjeev
2011-06-20 13:04 ` [PATCH 1/2] config: omap2+: force fb and dss support as Tomi Valkeinen
2011-06-21 5:12 ` [PATCH 1/2] config: omap2+: force fb and dss support as built-in Tushar Behera
2011-06-20 10:58 ` [PATCH 2/2] video: omap2: Compile omap2 support only when needed Tushar Behera
2011-06-20 13:06 ` Tomi Valkeinen [this message]
2011-06-21 4:49 ` Tushar Behera
2011-06-21 5:24 ` [PATCH 2/2] video: omap2: Compile omap2 support only when Tomi Valkeinen
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=1308575201.2076.57.camel@deskari \
--to=tomi.valkeinen@ti.com \
--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).