From: Hans Verkuil <hverkuil@xs4all.nl>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: [GIT PULL FOR v4.21 v2] Various fixes
Date: Fri, 23 Nov 2018 09:29:23 +0100 [thread overview]
Message-ID: <56ee9942-8afb-0456-80a2-757f83618fe8@xs4all.nl> (raw)
(fixed up my SoB mess)
Just one note: the "cec: keep track of outstanding transmits" is CC-ed to stable
for v4.18 and up, but I prefer to wait until v4.21 before merging it to give it
more test time. It is not something that happens in normal usage, so delaying
this isn't a problem.
Regards,
Hans
The following changes since commit fbe57dde7126d1b2712ab5ea93fb9d15f89de708:
media: ov7740: constify structures stored in fields of v4l2_subdev_ops structure (2018-11-06 07:17:02 -0500)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/br-v4.21a2
for you to fetch changes up to 9001e4d520f11d344f10092d3217156ec10c6934:
vivid: fill in media_device bus_info (2018-11-23 09:26:54 +0100)
----------------------------------------------------------------
Tag branch
----------------------------------------------------------------
Hans Verkuil (7):
adv7604: add CEC support for adv7611/adv7612
cec: report Vendor ID after initialization
cec: add debug_phys_addr module option
cec: keep track of outstanding transmits
vivid: fix error handling of kthread_run
vivid: set min width/height to a value > 0
vivid: fill in media_device bus_info
Julia Lawall (4):
media: vicodec: constify v4l2_ctrl_ops structure
media: rockchip/rga: constify v4l2_m2m_ops structure
media: vimc: constify structures stored in fields of v4l2_subdev_ops structure
media: rockchip/rga: constify video_device structure
Sean Young (1):
media: v4l uapi docs: few minor corrections and typos
Documentation/media/uapi/v4l/app-pri.rst | 2 +-
Documentation/media/uapi/v4l/audio.rst | 2 +-
Documentation/media/uapi/v4l/dev-capture.rst | 2 +-
Documentation/media/uapi/v4l/dev-teletext.rst | 2 +-
Documentation/media/uapi/v4l/format.rst | 2 +-
Documentation/media/uapi/v4l/mmap.rst | 22 +++++++++----------
Documentation/media/uapi/v4l/open.rst | 2 +-
Documentation/media/uapi/v4l/tuner.rst | 4 ++--
Documentation/media/uapi/v4l/userp.rst | 8 +++----
Documentation/media/uapi/v4l/video.rst | 4 ++--
drivers/media/cec/cec-adap.c | 34 ++++++++++++++++++++++--------
drivers/media/cec/cec-core.c | 6 ++++++
drivers/media/i2c/adv7604.c | 63 ++++++++++++++++++++++++++++++++++++++++++++++---------
drivers/media/platform/rockchip/rga/rga.c | 4 ++--
drivers/media/platform/vicodec/vicodec-core.c | 2 +-
drivers/media/platform/vimc/vimc-sensor.c | 2 +-
drivers/media/platform/vivid/vivid-core.c | 2 ++
drivers/media/platform/vivid/vivid-kthread-cap.c | 5 ++++-
drivers/media/platform/vivid/vivid-kthread-out.c | 5 ++++-
drivers/media/platform/vivid/vivid-vid-common.c | 2 +-
include/media/cec.h | 1 +
21 files changed, 125 insertions(+), 51 deletions(-)
next reply other threads:[~2018-11-23 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 8:29 Hans Verkuil [this message]
2018-11-23 8:33 [GIT PULL FOR v4.21 v2] Various fixes 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=56ee9942-8afb-0456-80a2-757f83618fe8@xs4all.nl \
--to=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).