The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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.18-rc5] media fixes
Date: Wed, 5 Nov 2025 10:17:13 +0100	[thread overview]
Message-ID: <20251105101713.6527cb26@foz.lan> (raw)

[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]

Hi Linus,

Please pull from:

	git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media.git media/v6.18-2

For:

- honour privacy led with pdx86/int3472;
- fix invalid file access on cx18 and ivtv;
- forbid remove_bufs when legacy fileio is active on videbuf2;
- add an heuristic to find stream entity on uvcvideo.

Regards,
Mauro

---

The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:

  Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media.git tags/media/v6.18-2

for you to fetch changes up to 27afd6e066cfd80ddbe22a4a11b99174ac89cced:

  media: videobuf2: forbid remove_bufs when legacy fileio is active (2025-10-24 11:16:26 +0200)

----------------------------------------------------------------
[GIT PULL for v6.18-rc5] media fixes

----------------------------------------------------------------
Hans de Goede (1):
      media: v4l2-subdev / pdx86: int3472: Use "privacy" as con_id for the privacy LED

Jacopo Mondi (2):
      media: cx18: Fix invalid access to file *
      media: ivtv: Fix invalid access to file *

Marek Szyprowski (1):
      media: videobuf2: forbid remove_bufs when legacy fileio is active

Ricardo Ribalda (1):
      media: uvcvideo: Use heuristic to find stream entity

 drivers/media/common/videobuf2/videobuf2-v4l2.c |  5 +++++
 drivers/media/pci/cx18/cx18-driver.c            |  9 +++-----
 drivers/media/pci/cx18/cx18-ioctl.c             | 30 ++++++++++++++++---------
 drivers/media/pci/cx18/cx18-ioctl.h             |  8 ++++---
 drivers/media/pci/ivtv/ivtv-driver.c            | 11 ++++-----
 drivers/media/pci/ivtv/ivtv-ioctl.c             | 22 +++++++++++++-----
 drivers/media/pci/ivtv/ivtv-ioctl.h             |  6 +++--
 drivers/media/usb/uvc/uvc_driver.c              | 15 ++++++++++++-
 drivers/media/v4l2-core/v4l2-subdev.c           |  2 +-
 drivers/platform/x86/intel/int3472/led.c        |  2 +-
 10 files changed, 73 insertions(+), 37 deletions(-)

[-- Attachment #2: tmpfile.00000674-image.xpm --]
[-- Type: image/xpm, Size: 365003 bytes --]

[-- Attachment #3: tmpfile.00000677-image.xpm --]
[-- Type: image/xpm, Size: 365003 bytes --]

             reply	other threads:[~2025-11-05  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05  9:17 Mauro Carvalho Chehab [this message]
2025-11-05 10:00 ` [GIT PULL for v6.18-rc5] 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=20251105101713.6527cb26@foz.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