[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1415369269-5064-11-git-send-email-boris.brezillon@free-electrons.com>
Date: Fri, 7 Nov 2014 15:07:49 +0100
From: Boris Brezillon <boris.brezillon@...e-electrons.com>
To: Mauro Carvalho Chehab <m.chehab@...sung.com>,
Hans Verkuil <hans.verkuil@...co.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
linux-media@...r.kernel.org, Sakari Ailus <sakari.ailus@....fi>
Cc: linux-arm-kernel@...ts.infradead.org, linux-api@...r.kernel.org,
devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org,
Guennadi Liakhovetski <g.liakhovetski@....de>,
Boris Brezillon <boris.brezillon@...e-electrons.com>
Subject: [PATCH v3 10/10] [media] v4l: Forbid usage of V4L2_MBUS_FMT definitions inside the kernel
Place v4l2_mbus_pixelcode in a #ifndef __KERNEL__ section so that kernel
users don't have access to these definitions.
We have to keep this definition for user-space users even though they're
encouraged to move to the new media_bus_format enum.
Signed-off-by: Boris Brezillon <boris.brezillon@...e-electrons.com>
---
include/uapi/linux/v4l2-mediabus.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/include/uapi/linux/v4l2-mediabus.h b/include/uapi/linux/v4l2-mediabus.h
index 3d87db7..4f31d0e 100644
--- a/include/uapi/linux/v4l2-mediabus.h
+++ b/include/uapi/linux/v4l2-mediabus.h
@@ -15,6 +15,14 @@
#include <linux/videodev2.h>
#include <linux/media-bus-format.h>
+#ifndef __KERNEL__
+
+/*
+ * enum v4l2_mbus_pixelcode and its defintions are now deprecated, and
+ * MEDIA_BUS_FMT_ defintions (defined in media-bus-format.h) should be
+ * used instead.
+ */
+
#define V4L2_MBUS_FROM_MEDIA_BUS_FMT(name) \
MEDIA_BUS_FMT_ ## name = V4L2_MBUS_FMT_ ## name
@@ -102,6 +110,7 @@ enum v4l2_mbus_pixelcode {
V4L2_MBUS_FROM_MEDIA_BUS_FMT(AHSV8888_1X32),
};
+#endif /* __KERNEL__ */
/**
* struct v4l2_mbus_framefmt - frame format on the media bus
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists