From: Randy Dunlap <rdunlap@infradead.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>, linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl, Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Wentong Wu <wentong.wu@intel.com>,
Zhifeng Wang <zhifeng.wang@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH 1/1] media: via: Use correct dependency for camera sensor drivers
Date: Tue, 22 Aug 2023 14:01:16 -0700 [thread overview]
Message-ID: <1812e39f-ddbc-d655-5d04-0a13d04437ab@infradead.org> (raw)
In-Reply-To: <20230822081034.3869843-1-sakari.ailus@linux.intel.com>
On 8/22/23 01:10, Sakari Ailus wrote:
> The via camera controller driver selected ov7670 driver, however now that
> driver has dependencies and may no longer be selected unconditionally.
>
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Fixes: 7d3c7d2a2914 ("media: i2c: Add a camera sensor top level menu")
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> drivers/media/platform/via/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/via/Kconfig b/drivers/media/platform/via/Kconfig
> index 8926eb0803b2..6e603c038248 100644
> --- a/drivers/media/platform/via/Kconfig
> +++ b/drivers/media/platform/via/Kconfig
> @@ -7,7 +7,7 @@ config VIDEO_VIA_CAMERA
> depends on V4L_PLATFORM_DRIVERS
> depends on FB_VIA && VIDEO_DEV
> select VIDEOBUF2_DMA_SG
> - select VIDEO_OV7670
> + select VIDEO_OV7670 if VIDEO_CAMERA_SENSOR
> help
> Driver support for the integrated camera controller in VIA
> Chrome9 chipsets. Currently only tested on OLPC xo-1.5 systems
--
~Randy
prev parent reply other threads:[~2023-08-22 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 8:10 Sakari Ailus
2023-08-22 21:01 ` Randy Dunlap [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=1812e39f-ddbc-d655-5d04-0a13d04437ab@infradead.org \
--to=rdunlap@infradead.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sfr@canb.auug.org.au \
--cc=wentong.wu@intel.com \
--cc=zhifeng.wang@intel.com \
/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
all inboxes | Powered by JetHome®