From: Greg KH <gregkh@linuxfoundation.org>
To: Sean Young <sean@mess.org>
Cc: mchehab@s-opensource.com, stable@vger.kernel.org, user.vdr@gmail.com
Subject: Re: FAILED: patch "[PATCH] media: lirc: LIRC_GET_REC_RESOLUTION should return" failed to apply to 4.4-stable tree
Date: Tue, 8 Aug 2017 09:15:35 -0700 [thread overview]
Message-ID: <20170808161535.GD20707@kroah.com> (raw)
In-Reply-To: <20170808091336.r5casujzewg5ugfk@gofer.mess.org>
On Tue, Aug 08, 2017 at 10:13:36AM +0100, Sean Young wrote:
> >From dfd1bd8275a6287068fda370ac49a8549e660674 Mon Sep 17 00:00:00 2001
> From: Sean Young <sean@mess.org>
> Date: Fri, 7 Jul 2017 18:49:18 -0300
> Subject: [PATCH] media: lirc: LIRC_GET_REC_RESOLUTION should return
> microseconds
>
> Since commit e8f4818895b3 ("[media] lirc: advertise
> LIRC_CAN_GET_REC_RESOLUTION and improve") lircd uses the ioctl
> LIRC_GET_REC_RESOLUTION to determine the shortest pulse or space that
> the hardware can detect. This breaks decoding in lirc because lircd
> expects the answer in microseconds, but nanoseconds is returned.
>
> Cc: <stable@vger.kernel.org> # v2.6.36+
> Reported-by: Derek <user.vdr@gmail.com>
> Tested-by: Derek <user.vdr@gmail.com>
> Signed-off-by: Sean Young <sean@mess.org>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> ---
> drivers/media/rc/ir-lirc-codec.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks for the 2 backports, now applied.
greg k-h
prev parent reply other threads:[~2017-08-08 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 22:14 FAILED: patch "[PATCH] media: lirc: LIRC_GET_REC_RESOLUTION should return" failed to apply to 4.4-stable tree gregkh
2017-08-08 9:13 ` Sean Young
2017-08-08 16:15 ` Greg KH [this message]
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=20170808161535.GD20707@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mchehab@s-opensource.com \
--cc=sean@mess.org \
--cc=stable@vger.kernel.org \
--cc=user.vdr@gmail.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).