From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Subject: [GIT FIXES v2 FOR 6.6] Various fixes, including for Kconfig
Date: Fri, 29 Sep 2023 10:54:48 +0000 [thread overview]
Message-ID: <ZRas+EVecmwdH8+b@valkosipuli.retiisi.eu> (raw)
Hi Mauro, Hans,
Here are a couple of fixes for 6.6, two of which fix Kconfig dependency
issues that lead to build failures.
since v1:
- Fix Fixes: tag in the ivsc patch.
- Add the tegra-video patch.
Please pull.
The following changes since commit 263cb0cc5abac7c22a6c0dfa7e50e89d8e6c6900:
media: imx-mipi-csis: Remove an incorrect fwnode_handle_put() call (2023-09-19 09:03:21 +0200)
are available in the Git repository at:
git://linuxtv.org/sailus/media_tree.git tags/fixes-6.6-2.3-signed
for you to fetch changes up to ad85af4f94d7d527fc43e0291b492fd02cc8f0de:
staging: media: tegra-video: fix infinite recursion regression (2023-09-29 12:17:53 +0300)
----------------------------------------------------------------
V4L2 fixes for 6.6
----------------------------------------------------------------
Arnd Bergmann (1):
media: pci: intel: ivsc: select V4L2_FWNODE
Christophe JAILLET (1):
media: pxa_camera: Fix an error handling path in pxa_camera_probe()
Luca Ceresoli (1):
staging: media: tegra-video: fix infinite recursion regression
Sakari Ailus (1):
media: ipu-bridge: Fix Kconfig dependencies
drivers/media/pci/intel/Kconfig | 20 ++++++++++++++------
drivers/media/pci/intel/ipu3/Kconfig | 21 +--------------------
drivers/media/pci/intel/ivsc/Kconfig | 2 +-
drivers/media/platform/intel/pxa_camera.c | 2 +-
drivers/staging/media/atomisp/Kconfig | 2 +-
drivers/staging/media/tegra-video/vi.c | 16 ++++++++++------
6 files changed, 28 insertions(+), 35 deletions(-)
--
Sakari Ailus
next reply other threads:[~2023-09-29 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 10:54 Sakari Ailus [this message]
2023-09-29 11:20 ` [GIT FIXES v2 FOR 6.6] Various fixes, including for Kconfig (#95326) Jenkins
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=ZRas+EVecmwdH8+b@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=linux-media@vger.kernel.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 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.