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 v6.10-rc7] media fixes
Date: Wed, 3 Jul 2024 08:23:29 +0200 [thread overview]
Message-ID: <20240703082329.20b1bc37@coco.lan> (raw)
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.10-3
For some fixes related to the IPU6 driver.
Regards,
Mauro
The following changes since commit 83a7eefedc9b56fe7bfeff13b6c7356688ffa670:
Linux 6.10-rc3 (2024-06-09 14:19:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.10-3
for you to fetch changes up to fd404435d44b453d62afe77545b9252c2cc72c8a:
media: ivsc: Depend on IPU_BRIDGE or not IPU_BRIDGE (2024-06-15 11:51:23 +0200)
----------------------------------------------------------------
media fixes for v6.10-rc7
----------------------------------------------------------------
Hao Ge (1):
media: intel/ipu6: Fix a null pointer dereference in ipu6_isys_query_stream_by_source
Sakari Ailus (2):
media: ipu6: Use the ISYS auxdev device as the V4L2 device's device
media: ivsc: Depend on IPU_BRIDGE or not IPU_BRIDGE
drivers/media/pci/intel/ipu6/ipu6-isys-video.c | 2 +-
drivers/media/pci/intel/ipu6/ipu6-isys.c | 2 +-
drivers/media/pci/intel/ivsc/Kconfig | 1 +
3 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2024-07-03 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 6:23 Mauro Carvalho Chehab [this message]
2024-07-03 7:16 ` [GIT PULL for v6.10-rc7] media fixes (#102880) Jenkins
2024-07-03 17:32 ` [GIT PULL for v6.10-rc7] media fixes pr-tracker-bot
2024-07-15 8:08 ` [GIT PULL for v6.10-rc7] media fixes (#102880) 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=20240703082329.20b1bc37@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 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.