From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/5] omap2plus_defconfig: Enable omap3isp and MT9T111 sensor drivers
Date: Tue, 20 Sep 2011 16:52:54 -0700 [thread overview]
Message-ID: <20110920235254.GM2937@atomide.com> (raw)
In-Reply-To: <201109210113.49151.laurent.pinchart@ideasonboard.com>
* Laurent Pinchart <laurent.pinchart@ideasonboard.com> [110920 15:40]:
> > CONFIG_REGULATOR_TPS65023=y
> > CONFIG_REGULATOR_TPS6507X=y
> > +CONFIG_MEDIA_SUPPORT=y
> > +CONFIG_MEDIA_CONTROLLER=y
> > +CONFIG_VIDEO_DEV=y
> > +CONFIG_VIDEO_V4L2_COMMON=y
> > +CONFIG_VIDEO_ALLOW_V4L1=y
> > +CONFIG_VIDEO_V4L1_COMPAT=y
> > +CONFIG_VIDEO_V4L2_SUBDEV_API=y
> > +CONFIG_VIDEO_MEDIA=y
> > +CONFIG_VIDEO_MT9T111=y
> > +CONFIG_VIDEO_OMAP3=y
>
> Shouldn't they be compiled as modules instead ?
Yes, let's not apply this.
Tony
prev parent reply other threads:[~2011-09-20 23:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 14:56 [PATCH 0/5] OMAP3EVM: Add support for MT9T111 sensor Deepthy Ravi
2011-09-20 14:56 ` [PATCH 1/5] omap3evm: Enable regulators for camera interface Deepthy Ravi
2011-09-20 14:56 ` [PATCH 2/5] [media] v4l: Add mt9t111 sensor driver Deepthy Ravi
2011-09-20 15:09 ` Guennadi Liakhovetski
2011-09-27 14:07 ` Ravi, Deepthy
2011-09-20 14:56 ` [PATCH 3/5] omap3evm: Add Camera board init/hookup file Deepthy Ravi
2011-09-20 14:56 ` [PATCH 4/5] ispccdc: Configure CCDC_SYN_MODE register for UYVY8_2X8 and YUYV8_2X8 formats Deepthy Ravi
2011-09-20 23:26 ` Laurent Pinchart
2011-09-21 5:32 ` Ravi, Deepthy
2011-09-21 9:06 ` Laurent Pinchart
2011-09-23 11:53 ` Ravi, Deepthy
2011-09-20 14:56 ` [PATCH 5/5] omap2plus_defconfig: Enable omap3isp and MT9T111 sensor drivers Deepthy Ravi
2011-09-20 23:13 ` Laurent Pinchart
2011-09-20 23:52 ` Tony Lindgren [this message]
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=20110920235254.GM2937@atomide.com \
--to=tony@atomide.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).