From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Ricardo Ribalda <ribalda@chromium.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: [GIT FIXES FOR 6.10] IPU6 and Unicam fixes
Date: Thu, 2 May 2024 08:35:57 +0000 [thread overview]
Message-ID: <ZjNQbS9CF1U6lGWx@valkosipuli.retiisi.eu> (raw)
Hi Hans, Mauro,
Here are a few fixes for the IPU6 and Unicam drivers, for issues found
since merging them. Most are are due to Kconfig options.
Please pull.
The following changes since commit a1c6d22421501fc1016b99ac8570a1030714c70f:
media: staging: max96712: fix copy-paste error (2024-04-30 14:33:08 +0100)
are available in the Git repository at:
git://linuxtv.org/sailus/media_tree.git tags/fixes-6.10-1.1-signed
for you to fetch changes up to f28348ebadf7c7127646672f363e055cb19f3b66:
media: intel/ipu6: Fix build with !ACPI (2024-05-02 11:34:26 +0300)
----------------------------------------------------------------
IPU6 and Unicam fixes
----------------------------------------------------------------
Laurent Pinchart (1):
media: bcm2835-unicam: Include v4l2-subdev.h
Ricardo Ribalda (4):
media: bcm2835-unicam: Fix build with !PM
media: intel/ipu6: Switch to RUNTIME_PM_OPS() and SYSTEM_SLEEP_PM_OPS
media: intel/ipu6: Fix direct dependency Kconfig error
media: intel/ipu6: Fix build with !ACPI
Sakari Ailus (1):
media: intel/ipu6: Fix vmalloc memory allocation
drivers/media/pci/intel/Kconfig | 3 +-
drivers/media/pci/intel/ipu-bridge.c | 66 +++++++++++++++++-------
drivers/media/pci/intel/ipu6/ipu6.c | 6 +--
drivers/media/platform/broadcom/bcm2835-unicam.c | 3 +-
4 files changed, 54 insertions(+), 24 deletions(-)
--
Kind regards,
Sakari Ailus
next reply other threads:[~2024-05-02 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 8:35 Sakari Ailus [this message]
2024-05-02 9:15 ` [GIT FIXES FOR 6.10] IPU6 and Unicam fixes (#101452) Jenkins
2024-05-02 10:25 ` [GIT FIXES FOR 6.10] IPU6 and Unicam fixes Mauro Carvalho Chehab
2024-05-02 10:37 ` Sakari Ailus
2024-05-02 11:42 ` Mauro Carvalho Chehab
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=ZjNQbS9CF1U6lGWx@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@chromium.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 read-only IMAP folder(s) and NNTP newsgroup(s).