public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
To: Jean Delvare <khali@linux-fr.org>
Cc: Andrew Morton <akpm@osdl.org>,
	js@linuxtv.org, LM Sensors <lm-sensors@lm-sensors.org>,
	Greg KH <gregkh@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 11/31] V4L (0999) Some funcions now static and I2C hw code for IR
Date: Thu, 01 Dec 2005 17:21:07 -0200	[thread overview]
Message-ID: <1133464867.23362.15.camel@localhost> (raw)
In-Reply-To: <20051201201121.1c09cec7.khali@linux-fr.org>

Em Qui, 2005-12-01 às 20:11 +0100, Jean Delvare escreveu:
> Hi Mauro,
> 
> [As a side note, it looks like there have been some distribution
> problems with this patchset... I can only see 0/31 (twice) on LKML and
> 11/31 didn't make it to the lm-sensors list as it was supposed to. I
> received it twice though.]
	In fact, all were sent to lkml... for some unknown reason, my ISP
didn't sent it (or lkml anti-spam rules filtered?). I even tried to send
a second time...
> 
> > From: Mauro Carvalho Chehab <mchehab@brturbo.com.br>
> >
> > - Some funcions are now declared as static
> > - Added a I2C code for InfraRed.
> 
> Unrelated changes, this should have been two separate patches. Also,
> "I2C driver ID" would better describe what the second change is about
> than "I2C code".
	Ok. I'll do it next time. I tried to consolidate into one due the
ammount of patches we have to send. Up now, we sent more than 250
patches, just v4l updates to 2.6.15.
> 
> > --- git.orig/drivers/media/video/ir-kbd-i2c.c
> > +++ git/drivers/media/video/ir-kbd-i2c.c
> > @@ -278,7 +278,7 @@ static int ir_probe(struct i2c_adapter *
> >
> > static struct i2c_driver driver = {
> > 	.name           = "ir remote kbd driver",
> > -	.id             = I2C_DRIVERID_EXP3, /* FIXME */
> > +	.id             = I2C_DRIVERID_I2C_IR,
> > 	.flags          = I2C_DF_NOTIFY,
> > 	.attach_adapter = ir_probe,
> > 	.detach_client  = ir_detach,
> 
> That's a poor ID name you chose. The second "I2C" is totally redundant,
> and "IR" is a bit short and could mean about anything. Please change it to
> I2C_DRIVERID_IRKBD or I2C_DRIVERID_INFRARED or something.
	Ok. (We have also other non-i2c ir.. that's why I called it I2C_IR).
I'll prepare a patch for it. I2C_DRIVERID_INFRARED seems a good name.
> 
> Thanks,
Cheers, 
Mauro.


      reply	other threads:[~2005-12-02  1:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1133400730.21135.62.camel@localhost>
2005-12-01 19:11 ` [Patch 11/31] V4L (0999) Some funcions now static and I2C hw code for IR Jean Delvare
2005-12-01 19:21   ` 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=1133464867.23362.15.camel@localhost \
    --to=mchehab@brturbo.com.br \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=js@linuxtv.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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