linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-media@vger.kernel.org
Subject: [GIT PULL FOR v4.11] More RC updates
Date: Mon, 30 Jan 2017 22:05:21 +0000	[thread overview]
Message-ID: <20170130220521.GB20904@gofer.mess.org> (raw)

Hi Mauro,

This includes a fix for my embarrassing ir-rx51 build failure, the mediatek
IR driver, a keymap and some important fixes for tx-only drivers.

Thanks,

Sean


The following changes since commit a052af2a548decf1da5cccf9e777aa02321e3ffb:

  [media] staging/media/s5p-cec/exynos_hdmi_cecctrl.c Fixed blank line before closing brace '}' (2017-01-30 15:48:54 -0200)

are available in the git repository at:

  git://linuxtv.org/syoung/media_tree.git for-v4.11b

for you to fetch changes up to 7813bce59dca0eb7f9af1626fc9cd6ef1ddea9a5:

  [media] rx51: broken build (2017-01-30 21:38:30 +0000)

----------------------------------------------------------------
Martin Blumenstingl (1):
      [media] rc/keymaps: add a keytable for the GeekBox remote control

Sean Wang (3):
      [media] rc: add driver for IR remote receiver on MT7623 SoC
      [media] Documentation: devicetree: move shared property used by rc into a common place
      [media] Documentation: devicetree: Add document bindings for mtk-cir

Sean Young (5):
      [media] lirc: fix transmit-only read features
      [media] rc: remove excessive spaces from error message
      [media] lirc: LIRC_GET_MIN_TIMEOUT should be in range
      [media] lirc: fix null dereference for tx-only devices
      [media] rx51: broken build

 .../devicetree/bindings/media/gpio-ir-receiver.txt |   3 +-
 .../devicetree/bindings/media/hix5hd2-ir.txt       |   2 +-
 .../devicetree/bindings/media/mtk-cir.txt          |  24 ++
 Documentation/devicetree/bindings/media/rc.txt     | 116 +++++++
 .../devicetree/bindings/media/sunxi-ir.txt         |   2 +-
 arch/arm/mach-omap2/pdata-quirks.c                 |   2 +-
 drivers/media/rc/Kconfig                           |  11 +
 drivers/media/rc/Makefile                          |   1 +
 drivers/media/rc/ir-lirc-codec.c                   |   7 +-
 drivers/media/rc/keymaps/Makefile                  |   1 +
 drivers/media/rc/keymaps/rc-geekbox.c              |  55 ++++
 drivers/media/rc/lirc_dev.c                        |   2 +-
 drivers/media/rc/mtk-cir.c                         | 335 +++++++++++++++++++++
 drivers/media/rc/rc-main.c                         |   3 +-
 include/media/rc-map.h                             |   1 +
 15 files changed, 555 insertions(+), 10 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/media/mtk-cir.txt
 create mode 100644 Documentation/devicetree/bindings/media/rc.txt
 create mode 100644 drivers/media/rc/keymaps/rc-geekbox.c
 create mode 100644 drivers/media/rc/mtk-cir.c

             reply	other threads:[~2017-01-30 22:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30 22:05 Sean Young [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-02-03 13:13 [GIT PULL FOR v4.11] More RC updates Sean Young

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=20170130220521.GB20904@gofer.mess.org \
    --to=sean@mess.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).