From: Mauro Carvalho Chehab <mchehab+huawei@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 v5.9-rc7] media fixes
Date: Thu, 24 Sep 2020 14:38:34 +0200 [thread overview]
Message-ID: <20200924143834.79ef0744@coco.lan> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v5.9-3
It fixes a regression at the CEC adapter core:
media: cec-adap.c: don't use flush_scheduled_work()
While not too late, it also contains two uAPI patches for the
changes already merged for Kernel 5.9:
media: dt-bindings: media: imx274: Convert to json-schema
media: media/v4l2: remove V4L2_FLAG_MEMORY_NON_CONSISTENT flag
The first one has a change to lowercase on one of the DT new
additions for Kernel 5.9. The second one actually reverts one
uAPI change that was nacked by mm people, because the changeset
has problems.
Thanks!
Mauro
---
The following changes since commit ddecfc76979d5585847c76c4c489dcac389f86dd:
media: mceusb: Avoid GFP_ATOMIC where it is not needed (2020-08-28 14:06:36 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v5.9-3
for you to fetch changes up to d0254f82d702a1d0d92e42f87676111de88846cf:
media: dt-bindings: media: imx274: Convert to json-schema (2020-09-22 11:13:46 +0200)
----------------------------------------------------------------
media fixes for v5.9-rc7
----------------------------------------------------------------
Hans Verkuil (1):
media: cec-adap.c: don't use flush_scheduled_work()
Jacopo Mondi (1):
media: dt-bindings: media: imx274: Convert to json-schema
Sergey Senozhatsky (1):
media: media/v4l2: remove V4L2_FLAG_MEMORY_NON_CONSISTENT flag
.../devicetree/bindings/media/i2c/imx274.txt | 38 -----------
.../devicetree/bindings/media/i2c/sony,imx274.yaml | 76 ++++++++++++++++++++++
Documentation/userspace-api/media/v4l/buffer.rst | 17 -----
.../userspace-api/media/v4l/vidioc-create-bufs.rst | 6 +-
.../userspace-api/media/v4l/vidioc-reqbufs.rst | 12 +---
MAINTAINERS | 2 +-
drivers/media/cec/core/cec-adap.c | 2 +-
drivers/media/common/videobuf2/videobuf2-core.c | 46 ++-----------
.../media/common/videobuf2/videobuf2-dma-contig.c | 19 ------
drivers/media/common/videobuf2/videobuf2-dma-sg.c | 3 +-
drivers/media/common/videobuf2/videobuf2-v4l2.c | 18 +----
drivers/media/dvb-core/dvb_vb2.c | 2 +-
drivers/media/v4l2-core/v4l2-compat-ioctl32.c | 10 +--
drivers/media/v4l2-core/v4l2-ioctl.c | 5 +-
include/media/videobuf2-core.h | 7 +-
include/uapi/linux/videodev2.h | 13 +---
16 files changed, 101 insertions(+), 175 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/media/i2c/imx274.txt
create mode 100644 Documentation/devicetree/bindings/media/i2c/sony,imx274.yaml
next reply other threads:[~2020-09-24 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 12:38 Mauro Carvalho Chehab [this message]
2020-09-24 16:27 ` [GIT PULL for v5.9-rc7] 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=20200924143834.79ef0744@coco.lan \
--to=mchehab+huawei@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;
as well as URLs for NNTP newsgroup(s).