All of lore.kernel.org
 help / color / mirror / Atom feed
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.8-rc5] media fixes
Date: Sat, 17 Feb 2024 10:08:08 +0100	[thread overview]
Message-ID: <20240217100808.58ef40b6@coco.lan> (raw)

Hi Linus,

Please pull from:
  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.8-4

For:

- a regression fix at rkisp1 shared IRQ logic;
- a breakage fix on atomisp due to a kAPI change;
- a permission fix for remote controller BPF support;
- a memleak on ir_toy driver;
- a Kconfig dependency on pwm-ir-rx.

The following changes since commit b32431b753217d8d45b018443b1a7aac215921fb:

  media: vb2: refactor setting flags and caps, fix missing cap (2024-01-24 17:27:51 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v6.8-4

for you to fetch changes up to 346c84e281a963437b9fe9dfcd92c531630289de:

  media: pwm-ir-tx: Depend on CONFIG_HIGH_RES_TIMERS (2024-02-01 13:49:39 +0100)

----------------------------------------------------------------
media fixes for v6.8-rc5

----------------------------------------------------------------
Hans de Goede (1):
      media: atomisp: Adjust for v4l2_subdev_state handling changes in 6.8

Sean Young (2):
      media: rc: bpf attach/detach requires write permission
      media: pwm-ir-tx: Depend on CONFIG_HIGH_RES_TIMERS

Tomi Valkeinen (2):
      media: Revert "media: rkisp1: Drop IRQF_SHARED"
      media:  : Fix IRQ handling due to shared interrupts

Zhipeng Lu (1):
      media: ir_toy: fix a memleak in irtoy_tx

 .../platform/rockchip/rkisp1/rkisp1-capture.c      |  3 ++
 .../media/platform/rockchip/rkisp1/rkisp1-common.h |  2 +
 .../media/platform/rockchip/rkisp1/rkisp1-csi.c    |  3 ++
 .../media/platform/rockchip/rkisp1/rkisp1-dev.c    | 24 ++++++++-
 .../media/platform/rockchip/rkisp1/rkisp1-isp.c    |  3 ++
 drivers/media/rc/Kconfig                           |  1 +
 drivers/media/rc/bpf-lirc.c                        |  6 +--
 drivers/media/rc/ir_toy.c                          |  2 +
 drivers/media/rc/lirc_dev.c                        |  5 +-
 drivers/media/rc/rc-core-priv.h                    |  2 +-
 drivers/staging/media/atomisp/pci/atomisp_cmd.c    | 58 ++++++++++++---------
 .../staging/media/atomisp/pci/atomisp_internal.h   |  4 +-
 drivers/staging/media/atomisp/pci/atomisp_ioctl.c  | 52 +++++++++++--------
 drivers/staging/media/atomisp/pci/atomisp_v4l2.c   | 59 ++++++++++++++++------
 14 files changed, 156 insertions(+), 68 deletions(-)


             reply	other threads:[~2024-02-17  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-17  9:08 Mauro Carvalho Chehab [this message]
2024-02-17  9:34 ` [GIT PULL for v6.8-rc5] media fixes (#99205) Jenkins
2024-02-17 16:27 ` [GIT PULL for v6.8-rc5] media fixes pr-tracker-bot
2024-04-09 13:54 ` [GIT PULL for v6.8-rc5] media fixes (#99205) 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=20240217100808.58ef40b6@coco.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 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.