All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Walls <awalls@md.metrocast.net>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Jarod Wilson <jarod@wilsonet.com>,
	Jean Delvare <khali@linux-fr.org>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Janne Grunau <j@jannau.net>, Jarod Wilson <jarod@redhat.com>
Subject: Re: [RFC PATCH] ir-kbd-i2c, lirc_zilog: Allow bridge drivers to pass an IR trasnceiver mutex to I2C IR modules
Date: Sun, 16 Jan 2011 14:29:27 -0500	[thread overview]
Message-ID: <1295206167.2400.36.camel@localhost> (raw)
In-Reply-To: <4D333877.6040900@redhat.com>

On Sun, 2011-01-16 at 16:27 -0200, Mauro Carvalho Chehab wrote:
> Jarod/Andy,
> 
> For now, I'm marking all those ir-kbd-i2c/lirc_zilog patches as "RFC" at patchwork,
> as I'm not sure if they're ok, and because there are a few revisions of them and
> I'm afraid to apply some wrong version.

And that's just fine. :)

That particular RFC was to get mostly Jean's opinion on adding fields to
struct IR_i2c_init_data and struct IR_i2c and code to ir-kbd-i2c.



> Please, after finishing and testing, send me a patch series or, preferably, a
> git pull with those stuff.

I just sent a [GIT PATCHES for 2.6.38], which is my pull request.  It
fixes one minor regression in ir-kbd-i2c.c.  The rest of the patches are
limited to lirc_zilog and do not modify any bridge drivers.  The
lirc_zilog changes were tested by me using my HVR-1600.

Jarrod will have to ask you to pull any hdpvr fixes, when he feels they
are ready.


Note my pull request does *not* include the patches in the subject [RFC
PATCH], so no worries about pulling those in. :)  I'll submit a pull for
those when they are correct and ready.


Regards,
Andy



      reply	other threads:[~2011-01-16 19:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16  3:49 [RFC PATCH] ir-kbd-i2c, lirc_zilog: Allow bridge drivers to pass an IR trasnceiver mutex to I2C IR modules Andy Walls
2011-01-16 18:27 ` Mauro Carvalho Chehab
2011-01-16 19:29   ` Andy Walls [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=1295206167.2400.36.camel@localhost \
    --to=awalls@md.metrocast.net \
    --cc=j@jannau.net \
    --cc=jarod@redhat.com \
    --cc=jarod@wilsonet.com \
    --cc=khali@linux-fr.org \
    --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.