linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jarod Wilson <jarod@redhat.com>
Cc: Greg KH <greg@kroah.com>,
	linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH 0/15] STAGING: add lirc device drivers
Date: Tue, 27 Jul 2010 16:24:23 -0300	[thread overview]
Message-ID: <4C4F3267.2060908@redhat.com> (raw)
In-Reply-To: <20100727181757.GD9465@redhat.com>

Em 27-07-2010 15:17, Jarod Wilson escreveu:
> On Tue, Jul 27, 2010 at 12:59:00PM -0300, Mauro Carvalho Chehab wrote:
>> Em 26-07-2010 20:25, Jarod Wilson escreveu:
>>> This patch series adds the remaining lirc_foo device drivers to the staging
>>> tree.
>>>  drivers/staging/lirc/TODO               |    8 +
> 
> ^^^
> 
>> Hi Jarod,
>>
>> Please add a TODO file at staging/lirc, describing what's needed for
>> the drivers to move to the IR branch.
> 
> See above. :)

Ops!

> It could use some further fleshing out though, particularly, some "known
> issues that must be fixed in this specific driver" type things.

Yes, but that's ok for now ;)

Cheers,
Mauro

      reply	other threads:[~2010-07-27 19:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 23:25 [PATCH 0/15] STAGING: add lirc device drivers Jarod Wilson
2010-07-26 23:26 ` [PATCH 01/15] staging/lirc: add lirc_bt829 driver Jarod Wilson
2010-07-26 23:27 ` [PATCH 02/15] staging/lirc: add lirc_ene0100 driver Jarod Wilson
2010-07-26 23:28 ` [PATCH 03/15] staging/lirc: add lirc_i2c driver Jarod Wilson
2010-07-26 23:29 ` [PATCH 04/15] staging/lirc: add lirc_igorplugusb driver Jarod Wilson
2010-07-26 23:29 ` [PATCH 05/15] staging/lirc: add lirc_imon driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 06/15] staging/lirc: add lirc_it87 driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 07/15] staging/lirc: add lirc_ite8709 driver Jarod Wilson
2010-07-26 23:30 ` [PATCH 08/15] staging/lirc: add lirc_parallel driver Jarod Wilson
2010-07-26 23:31 ` [PATCH 09/15] staging/lirc: add lirc_sasem driver Jarod Wilson
2010-07-26 23:31 ` [PATCH 10/15] staging/lirc: add lirc_serial driver Jarod Wilson
2010-07-26 23:32 ` [PATCH 11/15] staging/lirc: add lirc_sir driver Jarod Wilson
2010-07-26 23:32 ` [PATCH 12/15] staging/lirc: add lirc_streamzap driver Jarod Wilson
2010-07-26 23:33 ` [PATCH 13/15] staging/lirc: add lirc_ttusbir driver Jarod Wilson
2010-07-26 23:34 ` [PATCH 14/15] staging/lirc: add lirc_zilog driver Jarod Wilson
2010-07-26 23:34 ` [PATCH 15/15] staging/lirc: wire up Kconfig and Makefile bits Jarod Wilson
2010-07-27 15:59 ` [PATCH 0/15] STAGING: add lirc device drivers Mauro Carvalho Chehab
2010-07-27 16:09   ` Greg KH
2010-07-27 18:24     ` Jarod Wilson
2010-07-27 19:33       ` Mauro Carvalho Chehab
2010-07-27 19:51         ` Greg KH
2010-07-28  2:17           ` Jarod Wilson
2010-07-27 18:17   ` Jarod Wilson
2010-07-27 19:24     ` Mauro Carvalho Chehab [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=4C4F3267.2060908@redhat.com \
    --to=mchehab@redhat.com \
    --cc=greg@kroah.com \
    --cc=jarod@redhat.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).