From: Jarod Wilson <jarod@redhat.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 0/3] redrat3 driver updates for 3.1
Date: Thu, 14 Jul 2011 10:40:16 -0400 [thread overview]
Message-ID: <4E1EFFD0.6090501@redhat.com> (raw)
In-Reply-To: <4E1E2E3D.6030507@redhat.com>
Mauro Carvalho Chehab wrote:
> Em 13-07-2011 18:26, Jarod Wilson escreveu:
>> These changes make the redrat3 driver cooperate better with both in-kernel
>> and lirc userspace decoding of signals, tested with RC5, RC6 and NEC.
>> There's probably more we can do to make this a bit less hackish, but its
>> working quite well here for me right now.
>>
>> Jarod Wilson (3):
>> [media] redrat3: sending extra trailing space was useless
>> [media] redrat3: cap duration in the right place
>> [media] redrat3: improve compat with lirc userspace decode
>
>
> Applied, thanks. There's one small issue on it (32 bits compilation):
>
> drivers/media/rc/redrat3.c: In function ‘redrat3_init_rc_dev’:
> drivers/media/rc/redrat3.c:1106: warning: assignment from incompatible pointer type
> compilation succeeded
I've mainly been working atop 3.0-rc bits, so I wasn't getting that
warning. I believe that's new, following merge of one of David
Härdeman's patches that reworks tx a bit, iirc. I'll take care of that
as soon as I can.
--
Jarod Wilson
jarod@redhat.com
prev parent reply other threads:[~2011-07-14 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 21:26 [PATCH 0/3] redrat3 driver updates for 3.1 Jarod Wilson
2011-07-13 21:26 ` [PATCH 1/3] [media] redrat3: sending extra trailing space was useless Jarod Wilson
2011-07-13 21:26 ` [PATCH 2/3] [media] redrat3: cap duration in the right place Jarod Wilson
2011-07-13 21:26 ` [PATCH 3/3] [media] redrat3: improve compat with lirc userspace decode Jarod Wilson
2011-07-13 23:46 ` [PATCH 0/3] redrat3 driver updates for 3.1 Mauro Carvalho Chehab
2011-07-14 14:40 ` Jarod Wilson [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=4E1EFFD0.6090501@redhat.com \
--to=jarod@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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 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.