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.6-rc6] media fixes
Date: Fri, 13 Oct 2023 13:11:41 +0200 [thread overview]
Message-ID: <20231013131141.669dc1c9@sal.lan> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.6-5
For:
- a core fix: Don't report V4L2_SUBDEV_CAP_STREAMS when API is disabled;
- ipu-bridge: Add a missing acpi_dev_put();
- ov8858: fix driver for probe to work after 6.6-rc1;
- xilinx-vipp: fix async notifier logic.
Regards,
Mauro
---
The following changes since commit 10a6e5feccb877c3c75ad11d27942ad52c24815f:
Merge tag 'drm-fixes-2023-10-13' of git://anongit.freedesktop.org/drm/drm (2023-10-12 22:43:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.6-5
for you to fetch changes up to c46f16f156ac58afcf4addc850bb5dfbca77b9fc:
media: i2c: ov8858: Don't set fwnode in the driver (2023-10-11 15:26:16 +0200)
----------------------------------------------------------------
media fixes for v6.6-rc6
----------------------------------------------------------------
Geert Uytterhoeven (1):
media: ipu-bridge: Add missing acpi_dev_put() in ipu_bridge_get_ivsc_acpi_dev()
Hans de Goede (1):
media: subdev: Don't report V4L2_SUBDEV_CAP_STREAMS when the streams API is disabled
Ondrej Jirman (1):
media: i2c: ov8858: Don't set fwnode in the driver
Sakari Ailus (1):
media: xilinx-vipp: Look for entities also in waiting_list
drivers/media/i2c/ov8858.c | 10 ++--------
drivers/media/pci/intel/ipu-bridge.c | 4 +++-
drivers/media/platform/xilinx/xilinx-vipp.c | 17 ++++++++++++-----
drivers/media/v4l2-core/v4l2-subdev.c | 7 +++++++
4 files changed, 24 insertions(+), 14 deletions(-)
next reply other threads:[~2023-10-13 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 11:11 Mauro Carvalho Chehab [this message]
2023-10-13 11:53 ` [GIT PULL for v6.6-rc6] media fixes (#95897) Jenkins
2023-10-13 16:39 ` [GIT PULL for v6.6-rc6] 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=20231013131141.669dc1c9@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