public inbox for linux-kernel@vger.kernel.org
 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 v5.9-rc4] media fixes
Date: Thu, 3 Sep 2020 08:10:57 +0200	[thread overview]
Message-ID: <20200903081057.78407ab4@coco.lan> (raw)

Hi Linus,

Please pull from:
  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v5.9-2

For:

- a compilation fix issue with ti-vpe on arm 32 bits;
- two Kconfig fixes for imx214 and max9286 drivers;
- a kernel information leak at v4l2-core on time32 compat ioctls;
- some fixes at rc core unbind logic;
- a fix at mceusb driver for it to not use GFP_ATOMIC;
- fixes at cedrus and vicodec drivers at the control handling logic;
- a fix at gpio-ir-tx to avoid disabling interruts on a spinlock.

Thanks!
Mauro

The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:

  Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v5.9-2

for you to fetch changes up to ddecfc76979d5585847c76c4c489dcac389f86dd:

  media: mceusb: Avoid GFP_ATOMIC where it is not needed (2020-08-28 14:06:36 +0200)

----------------------------------------------------------------
media fixes for v5.9-rc4

----------------------------------------------------------------
Christophe JAILLET (1):
      media: mceusb: Avoid GFP_ATOMIC where it is not needed

Ezequiel Garcia (1):
      media: cedrus: Add missing v4l2_ctrl_request_hdl_put()

Hans Verkuil (1):
      media: vicodec: add missing v4l2_ctrl_request_hdl_put()

Jacopo Mondi (1):
      media: i2c: imx214: select V4L2_FWNODE

Laurent Pinchart (1):
      media: ti-vpe: cal: Fix compilation on 32-bit ARM

Peilin Ye (1):
      media: media/v4l2-core: Fix kernel-infoleak in video_put_user()

Sakari Ailus (1):
      media: max9286: Depend on OF_GPIO

Sean Young (3):
      media: rc: uevent sysfs file races with rc_unregister_device()
      media: rc: do not access device via sysfs after rc_unregister_device()
      media: gpio-ir-tx: spinlock is not needed to disable interrupts

 drivers/media/i2c/Kconfig                         |  4 +-
 drivers/media/platform/ti-vpe/cal.h               |  2 +-
 drivers/media/rc/gpio-ir-tx.c                     | 16 +++-----
 drivers/media/rc/mceusb.c                         |  2 +-
 drivers/media/rc/rc-main.c                        | 44 ++++++++++++--------
 drivers/media/test-drivers/vicodec/vicodec-core.c |  1 +
 drivers/media/v4l2-core/v4l2-ioctl.c              | 50 ++++++++++++-----------
 drivers/staging/media/sunxi/cedrus/cedrus.c       |  7 +++-
 8 files changed, 71 insertions(+), 55 deletions(-)


             reply	other threads:[~2020-09-03  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03  6:10 Mauro Carvalho Chehab [this message]
2020-09-03 17:09 ` [GIT PULL for v5.9-rc4] 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=20200903081057.78407ab4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox