From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL for v6.1-rc3] media fixes
Date: Thu, 27 Oct 2022 18:17:14 +0100 [thread overview]
Message-ID: <20221027181714.3d12aba5@sal.lan> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.1-3
For a bunch of patches addressing issues at the vivid driver and adding
new checks at V4L2 to validate the input parameters from some ioctls.
Regards,
Mauro
The following changes since commit 247f34f7b80357943234f93f247a1ae6b6c3a740:
Linux 6.1-rc2 (2022-10-23 15:27:33 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.1-3
for you to fetch changes up to de547896aac606a00435a219757a940ece142bf0:
media: vivid.rst: loop_video is set on the capture devnode (2022-10-25 16:43:54 +0100)
----------------------------------------------------------------
media fixes for v6.1-rc3
----------------------------------------------------------------
Hans Verkuil (8):
media: vivid: s_fbuf: add more sanity checks
media: vivid: dev->bitmap_cap wasn't freed in all cases
media: v4l2-dv-timings: add sanity checks for blanking values
media: videodev2.h: V4L2_DV_BT_BLANKING_HEIGHT should check 'interlaced'
media: vivid: fix control handler mutex deadlock
media: vivid: drop GFP_DMA32
media: vivid: set num_in/outputs to 0 if not supported
media: vivid.rst: loop_video is set on the capture devnode
Documentation/admin-guide/media/vivid.rst | 2 +-
drivers/media/test-drivers/vivid/vivid-core.c | 38 +++++++++++++++++++++---
drivers/media/test-drivers/vivid/vivid-core.h | 2 ++
drivers/media/test-drivers/vivid/vivid-osd.c | 2 +-
drivers/media/test-drivers/vivid/vivid-vid-cap.c | 35 ++++++++++++++++++----
drivers/media/v4l2-core/v4l2-dv-timings.c | 14 +++++++++
include/uapi/linux/videodev2.h | 3 +-
7 files changed, 83 insertions(+), 13 deletions(-)
next reply other threads:[~2022-10-27 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 17:17 Mauro Carvalho Chehab [this message]
2022-10-27 17:23 ` [GIT PULL for v6.1-rc3] media fixes (#86978) Jenkins
2022-10-27 20:50 ` [GIT PULL for v6.1-rc3] media fixes pr-tracker-bot
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=20221027181714.3d12aba5@sal.lan \
--to=mchehab@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=torvalds@linux-foundation.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