All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: linux-media@vger.kernel.org
Subject: [GIT PULL FOR v5.4] Various fixes DVB/RC
Date: Mon, 19 Aug 2019 12:31:26 +0100	[thread overview]
Message-ID: <20190819113126.fo3dvsux5eogcq5b@gofer.mess.org> (raw)

Hi Mauro,

This PR includes A Sun's re-write of mceusb Tx, some new keymaps and some
of fixes.

Thanks,
Sean

The following changes since commit 31d5d15dfc3418a57cfab419a353d8dc5f5698b5:

  media: MAINTAINERS: Add entry for the ov5670 driver (2019-08-15 08:17:04 -0300)

are available in the Git repository at:

  git://linuxtv.org/syoung/media_tree.git tags/v5.4d

for you to fetch changes up to 3bd8a3e22d3bb4b04604c1f35905a2083ce4600e:

  media: dvb-core: fix a memory leak bug (2019-08-19 12:08:24 +0100)

----------------------------------------------------------------
A Sun (1):
      mceusb: fix (eliminate) TX IR signal length limit

Christian Hewitt (7):
      media: rc: add keymap for Amediatech X96-MAX remote
      media: rc: add keymap for Khadas VIM/EDGE remote
      media: rc: add keymap for Tanix TX3 mini remote
      media: rc: add keymap for Tanix TX5 max remote
      media: rc: add keymap for WeTek Hub remote
      media: rc: add keymap for WeTeK Play 2 remote
      media: rc: add keymap for HardKernel ODROID remote

Marc Gonzalez (1):
      media: si2168: Refactor command setup code

Sean Young (2):
      media: dvb-frontends: use ida for pll number
      media: ttpci: unknown protocol is rc-mm-32

Wenwen Wang (3):
      media: dvb-frontends: fix memory leaks
      media: dvb-frontends: fix a memory leak bug
      media: dvb-core: fix a memory leak bug

 drivers/media/dvb-core/dvbdev.c             |   4 +-
 drivers/media/dvb-frontends/cx24117.c       |   4 +-
 drivers/media/dvb-frontends/dib7000p.c      |   7 +-
 drivers/media/dvb-frontends/dvb-pll.c       |  40 ++--
 drivers/media/dvb-frontends/si2168.c        | 159 ++++---------
 drivers/media/pci/ttpci/av7110_ir.c         |  14 +-
 drivers/media/rc/keymaps/Makefile           |   7 +
 drivers/media/rc/keymaps/rc-khadas.c        |  54 +++++
 drivers/media/rc/keymaps/rc-odroid.c        |  54 +++++
 drivers/media/rc/keymaps/rc-tanix-tx3mini.c |  77 +++++++
 drivers/media/rc/keymaps/rc-tanix-tx5max.c  |  68 ++++++
 drivers/media/rc/keymaps/rc-wetek-hub.c     |  53 +++++
 drivers/media/rc/keymaps/rc-wetek-play2.c   |  93 ++++++++
 drivers/media/rc/keymaps/rc-x96max.c        |  83 +++++++
 drivers/media/rc/mceusb.c                   | 334 ++++++++++++++++------------
 include/media/rc-map.h                      |   7 +
 16 files changed, 781 insertions(+), 277 deletions(-)
 create mode 100644 drivers/media/rc/keymaps/rc-khadas.c
 create mode 100644 drivers/media/rc/keymaps/rc-odroid.c
 create mode 100644 drivers/media/rc/keymaps/rc-tanix-tx3mini.c
 create mode 100644 drivers/media/rc/keymaps/rc-tanix-tx5max.c
 create mode 100644 drivers/media/rc/keymaps/rc-wetek-hub.c
 create mode 100644 drivers/media/rc/keymaps/rc-wetek-play2.c
 create mode 100644 drivers/media/rc/keymaps/rc-x96max.c

             reply	other threads:[~2019-08-19 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 11:31 Sean Young [this message]
2019-08-19 11:51 ` [GIT PULL FOR v5.4] Various fixes DVB/RC 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=20190819113126.fo3dvsux5eogcq5b@gofer.mess.org \
    --to=sean@mess.org \
    --cc=linux-media@vger.kernel.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.