All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: 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 v4.18-rc8] media fixes
Date: Thu, 2 Aug 2018 20:36:04 -0300	[thread overview]
Message-ID: <20180802203604.1d219a10@coco.lan> (raw)

Hi Linus,

Please pull from:
  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v4.18-3

For:

  - a dead lock regression at vsp1 driver;
  - some Remote Controller fixes related to the new BPF filter
    logic added on it for Kernel 4.18.

Thanks!
Mauro

-

The following changes since commit 7daf201d7fe8334e2d2364d4e8ed3394ec9af819:

  Linux 4.18-rc2 (2018-06-24 20:54:29 +0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media tags/media/v4.18-3

for you to fetch changes up to 8eb0e6421958e9777db98448a4030d8ae940c9a0:

  media: v4l: vsp1: Fix deadlock in VSPDL DRM pipelines (2018-07-30 08:22:59 -0400)

----------------------------------------------------------------
media fixes for v4.18-rc8

----------------------------------------------------------------
Laurent Pinchart (1):
      media: v4l: vsp1: Fix deadlock in VSPDL DRM pipelines

Sean Young (3):
      media: rc: be less noisy when driver misbehaves
      media: bpf: ensure bpf program is freed on detach
      media: rc: read out of bounds if bpf reports high protocol number

 drivers/media/platform/vsp1/vsp1_drm.c |  4 +---
 drivers/media/rc/bpf-lirc.c            |  1 +
 drivers/media/rc/rc-ir-raw.c           |  8 ++++----
 drivers/media/rc/rc-main.c             | 12 ++++++++++--
 4 files changed, 16 insertions(+), 9 deletions(-)

                 reply	other threads:[~2018-08-03  1:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180802203604.1d219a10@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=akpm@linux-foundation.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.