From: Tushar Behera <tushar.behera@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] video: Make omap2 support conditional
Date: Mon, 20 Jun 2011 10:57:59 +0000 [thread overview]
Message-ID: <1308566761-2850-1-git-send-email-tushar.behera@linaro.org> (raw)
Currently drivers/video/omap2 is built by default with every configuration
of the kernel. Current patchset makes the omap2 video support conditional
on appropriate config option.
[Patch 2/2] was first generated, but that resulted in a build error.
[Patch 1/2] was created to fix that build error.
These patches have only been tested for build consistency and have not been
tested on any related hardware.
Tushar Behera (2):
config: omap2+: force fb and dss support as built-in
video: omap2: Compile omap2 support only when needed
arch/arm/configs/omap2plus_defconfig | 4 ++--
drivers/video/Makefile | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-06-20 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 10:57 Tushar Behera [this message]
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 ` [PATCH 2/2] video: omap2: Compile omap2 support only when Tomi Valkeinen
2011-06-21 4:49 ` [PATCH 2/2] video: omap2: Compile omap2 support only when needed 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=1308566761-2850-1-git-send-email-tushar.behera@linaro.org \
--to=tushar.behera@linaro.org \
--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).