From: Hans Verkuil <hverkuil@xs4all.nl>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: [GIT PULL FOR v5.1] Various fixes
Date: Tue, 15 Jan 2019 09:16:04 +0100 [thread overview]
Message-ID: <0251b6cf-9084-2bf9-d61b-17926e1d718b@xs4all.nl> (raw)
Most notably Sakari's patch which adds V4L2_BUF_TYPE_META_OUTPUT to the
V4L2_TYPE_IS_OUTPUT define.
The other two are vivid fixes to make it pass the media regression test
I'm working on.
Regards,
Hans
The following changes since commit 1e0d0a5fd38192f23304ea2fc2b531fea7c74247:
media: s5p-mfc: fix incorrect bus assignment in virtual child device (2019-01-07 14:39:36 -0500)
are available in the Git repository at:
git://linuxtv.org/hverkuil/media_tree.git tags/br-v5.1d
for you to fetch changes up to 635891d4e3afdf9447f5cd6fd77735dca8e24850:
vivid: take data_offset into account for video output (2019-01-15 09:12:56 +0100)
----------------------------------------------------------------
Tag branch
----------------------------------------------------------------
Hans Verkuil (2):
vivid: disable VB2_USERPTR if dma_contig was configured
vivid: take data_offset into account for video output
Sakari Ailus (1):
v4l: uAPI: V4L2_BUF_TYPE_META_OUTPUT is an output buffer type
drivers/media/platform/vivid/vivid-core.c | 20 +++++++++++++++-----
drivers/media/platform/vivid/vivid-vid-out.c | 16 ++++++++++------
include/uapi/linux/videodev2.h | 3 ++-
3 files changed, 27 insertions(+), 12 deletions(-)
next reply other threads:[~2019-01-15 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 8:16 Hans Verkuil [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-18 17:04 [GIT PULL FOR v5.1] Various fixes Hans Verkuil
2019-02-07 15:31 Hans Verkuil
2019-01-31 14:10 Hans Verkuil
2019-01-16 16:03 Hans Verkuil
2019-01-10 12:34 Hans Verkuil
2019-01-10 11:18 Sean Young
2019-01-08 15:44 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=0251b6cf-9084-2bf9-d61b-17926e1d718b@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.