From: Sean Young <sean@mess.org>
To: linux-media@vger.kernel.org
Subject: [GIT PULL FOR v4.13] Various RC fixes
Date: Tue, 6 Jun 2017 22:22:44 +0100 [thread overview]
Message-ID: <20170606212244.GA843@gofer.mess.org> (raw)
Hi Mauro,
Some minor fixes that just missed the first pull request, that would be nice
to have in v4.13.
Thank you
Sean
The following changes since commit 9e9e6a78143bbb6cb9cffd29ab48d5f32def4e20:
[media] Doc*/media/uapi: fix control name (2017-06-06 16:49:46 -0300)
are available in the git repository at:
git://linuxtv.org/syoung/media_tree.git for-v4.13b
for you to fetch changes up to 8e35a2305e02ee0c8cb3bf971acab9fbe708e384:
[media] ir-spi: Fix issues with lirc API (2017-06-06 20:55:36 +0100)
----------------------------------------------------------------
Anton Blanchard (1):
[media] ir-spi: Fix issues with lirc API
Johan Hovold (2):
[media] mceusb: fix memory leaks in error path
[media] mceusb: drop redundant urb reinitialisation
Sean Young (1):
[media] sir_ir: annotate hardware config module parameters
drivers/media/rc/ir-spi.c | 9 ++++++---
drivers/media/rc/mceusb.c | 5 ++---
drivers/media/rc/sir_ir.c | 4 ++--
3 files changed, 10 insertions(+), 8 deletions(-)
reply other threads:[~2017-06-06 21:22 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=20170606212244.GA843@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox