From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: hverkuil@xs4all.nl
Subject: [PATCH 4/4] soc_camera: Depend on BROKEN
Date: Fri, 8 Feb 2019 10:41:47 +0200 [thread overview]
Message-ID: <20190208084147.9973-5-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20190208084147.9973-1-sakari.ailus@linux.intel.com>
This patch makes the SoC camera framework as well as effectively the few
remaining sensor drivers depend on BROKEN, rendering it uncompileable
without changes in Kconfig.
The purpose is to leave the code around if someone wishes to convert the
drivers to the modern day V4L2 sub-device framework without having to go
to see development history in git.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
drivers/staging/media/soc_camera/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/media/soc_camera/Kconfig b/drivers/staging/media/soc_camera/Kconfig
index 6a6aa6d2d150e..bacd30f0348dc 100644
--- a/drivers/staging/media/soc_camera/Kconfig
+++ b/drivers/staging/media/soc_camera/Kconfig
@@ -1,6 +1,6 @@
config SOC_CAMERA
tristate "SoC camera support"
- depends on VIDEO_V4L2 && HAS_DMA && I2C
+ depends on VIDEO_V4L2 && HAS_DMA && I2C && BROKEN
select VIDEOBUF2_CORE
help
SoC Camera is a common API to several cameras, not connecting
--
2.11.0
next prev parent reply other threads:[~2019-02-08 8:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 8:41 [PATCH 0/4] Move SoC camera to staging, depend on BROKEN Sakari Ailus
2019-02-08 8:41 ` [PATCH 1/4] soc_camera: Move to the staging tree Sakari Ailus
2019-02-08 8:41 ` [PATCH 2/4] soc_camera: Move the imx074 under soc_camera directory Sakari Ailus
2019-02-08 8:41 ` [PATCH 3/4] soc_camera: Move the mt9t031 " Sakari Ailus
2019-02-08 8:41 ` Sakari Ailus [this message]
2019-02-08 8:43 ` [PATCH 0/4] Move SoC camera to staging, depend on BROKEN Sakari Ailus
2019-02-08 8:52 ` Hans Verkuil
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=20190208084147.9973-5-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@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).