From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: backports@vger.kernel.org
Cc: julia.lawall@lip6.fr, oblinger@gmail.com,
"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: [PATCH 2/5] backports: address splitting of v4l2-mediabus.h to two files
Date: Thu, 20 Nov 2014 13:16:20 -0800 [thread overview]
Message-ID: <1416518183-7347-3-git-send-email-mcgrof@do-not-panic.com> (raw)
In-Reply-To: <1416518183-7347-1-git-send-email-mcgrof@do-not-panic.com>
From: "Luis R. Rodriguez" <mcgrof@suse.com>
The new file media-bus-format.h was derived from contents from
v4l2-mediabus.h, this change might be a bit harder to infer
exactly what to do but based on some contextual examination of
the file, if content integrity has not changed it should be
relatively easy to infer what to do with changes like this.
commit edcf58bc031e621f519c9dfce3c7e1ea6880c70a
Author: Boris BREZILLON <boris.brezillon@free-electrons.com>
Date: Mon Nov 10 14:28:26 2014 -0300
[media] Move mediabus format definition to a more standard place
Define MEDIA_BUS_FMT macros (re-using the values defined in the
v4l2_mbus_pixelcode enum) into a separate header file so that they can be
used from the DRM/KMS subsystem without any reference to the V4L2
subsystem.
Then set V4L2_MBUS_FMT definitions to the MEDIA_BUS_FMT values using the
V4L2_MBUS_FROM_MEDIA_BUS_FMT macro.
Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
include/uapi/linux/Kbuild | 1 +
include/uapi/linux/media-bus-format.h | 125 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
include/uapi/linux/v4l2-mediabus.h | 184 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------------------
3 files changed, 206 insertions(+), 104 deletions(-)
Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com>
---
copy-list | 1 +
1 file changed, 1 insertion(+)
diff --git a/copy-list b/copy-list
index b7ac165..19017af 100644
--- a/copy-list
+++ b/copy-list
@@ -145,6 +145,7 @@ include/uapi/linux/v4l2-common.h
include/uapi/linux/v4l2-controls.h
include/uapi/linux/v4l2-dv-timings.h
include/uapi/linux/v4l2-mediabus.h
+include/uapi/linux/media-bus-format.h
include/uapi/linux/v4l2-subdev.h
include/uapi/linux/videodev2.h
include/uapi/linux/vsp1.h
--
2.1.1
next prev parent reply other threads:[~2014-11-20 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 21:16 [PATCH 0/5] backports: move up to next-20141117 Luis R. Rodriguez
2014-11-20 21:16 ` [PATCH 1/5] backports: rename wpan-phy.h to cfg802154.h Luis R. Rodriguez
2014-11-20 21:22 ` Hauke Mehrtens
2014-11-20 21:31 ` Luis R. Rodriguez
2014-11-20 21:16 ` Luis R. Rodriguez [this message]
2014-11-20 21:16 ` [PATCH 3/5] backports: bump I2C_SI4713 to v3.13 Luis R. Rodriguez
2014-11-20 21:16 ` [PATCH 4/5] backports: backport netdev_rss_key_fill() Luis R. Rodriguez
2014-11-20 21:16 ` [PATCH 5/5] backports: refresh patches for next-20141117 Luis R. Rodriguez
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=1416518183-7347-3-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=backports@vger.kernel.org \
--cc=julia.lawall@lip6.fr \
--cc=mcgrof@suse.com \
--cc=oblinger@gmail.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