All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Patrick Lerda <patrick9876@free.fr>, linux-media@vger.kernel.org
Subject: [PATCH 0/2] rcmm with minor tweaks and selftest
Date: Thu, 17 Jan 2019 15:29:37 +0000	[thread overview]
Message-ID: <cover.1547738495.git.sean@mess.org> (raw)

Hi Patrick,

I've made some very minor/cosmetic changes and added rcmm to the selftest;
I didn't want to just add them to the tree without showing to you first.

Let me know what you think.

Thanks
Sean

Patrick Lerda (1):
  media: rc: rcmm decoder and encoder

Sean Young (1):
  selftests: Use lirc.h from kernel tree, not from system

 MAINTAINERS                              |   5 +
 drivers/media/rc/Kconfig                 |  13 ++
 drivers/media/rc/Makefile                |   1 +
 drivers/media/rc/ir-rcmm-decoder.c       | 254 +++++++++++++++++++++++
 drivers/media/rc/rc-core-priv.h          |   5 +
 drivers/media/rc/rc-main.c               |   9 +
 include/media/rc-map.h                   |  14 +-
 include/uapi/linux/lirc.h                |   6 +
 tools/include/uapi/linux/lirc.h          |  12 ++
 tools/testing/selftests/ir/Makefile      |   2 +
 tools/testing/selftests/ir/ir_loopback.c |   9 +
 11 files changed, 327 insertions(+), 3 deletions(-)
 create mode 100644 drivers/media/rc/ir-rcmm-decoder.c

-- 
2.20.1


             reply	other threads:[~2019-01-17 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 15:29 Sean Young [this message]
2019-01-17 15:29 ` [PATCH 1/2] selftests: Use lirc.h from kernel tree, not from system Sean Young
2019-01-22 15:51   ` shuah
2019-01-22 16:47     ` Sean Young
2019-01-17 15:29 ` [PATCH 2/2] media: rc: rcmm decoder and encoder Sean Young
2019-01-17 19:30 ` [PATCH 0/1] description update Patrick Lerda
2019-01-17 19:32   ` [PATCH 1/1] " Patrick Lerda

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=cover.1547738495.git.sean@mess.org \
    --to=sean@mess.org \
    --cc=linux-media@vger.kernel.org \
    --cc=patrick9876@free.fr \
    /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.