public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
	sensors@Stimpy.netroedge.com
Subject: Re: [BK PATCH] I2C update for 2.6.10-rc1
Date: Tue, 9 Nov 2004 07:21:45 -0800	[thread overview]
Message-ID: <20041109152145.GB27269@kroah.com> (raw)
In-Reply-To: <vYBFH9gE.1099992539.9943000.khali@gcu.info>

On Tue, Nov 09, 2004 at 10:29:00AM +0100, Jean Delvare wrote:
> 
> Hi Greg,
> 
> >Greg Kroah-Hartman:
> >  o I2C: delete normal_i2c_range logic from sensors as there are no more
> >         users
> >  o I2C: moved from all sensor drivers from normal_i2c_range to normal_i2c
> >  o I2C: fix i2c_detect to allow NULL fields in adapter address structure
> >  o I2C: remove normal_isa_range from I2C sensor drivers, as it's not used
> >  o I2C: remove ignore_range from I2C sensor drivers, as it's not used
> >  o I2C: remove probe_range from I2C sensor drivers, as it's not used
> 
> I'm very happy with that :) A documentation update will be needed though.

Doh, ok, I'll go do that, forgot that...

> Also, while we're at it, is there any reason why I2C_CLIENT_END and
> I2C_CLIENT_ISA_END are two different constants?

unsigned short vs unsigned int, right?

thanks,

greg k-h

      reply	other threads:[~2004-11-09 15:22 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-09  5:22 [BK PATCH] I2C update for 2.6.10-rc1 Greg KH
2004-11-09  5:24 ` [PATCH] " Greg KH
2004-11-09  5:24   ` Greg KH
2004-11-09  5:24     ` Greg KH
2004-11-09  5:24       ` Greg KH
2004-11-09  5:24         ` Greg KH
2004-11-09  5:24           ` Greg KH
2004-11-09  5:24             ` Greg KH
2004-11-09  5:24               ` Greg KH
2004-11-09  5:24                 ` Greg KH
2004-11-09  5:24                   ` Greg KH
2004-11-09  5:24                     ` Greg KH
2004-11-09  5:24                       ` Greg KH
2004-11-09  5:24                         ` Greg KH
2004-11-09  5:24                           ` Greg KH
2004-11-09  5:24                             ` Greg KH
2004-11-09  5:24                               ` Greg KH
2004-11-09  5:24                                 ` Greg KH
2004-11-09  5:24                                   ` Greg KH
2004-11-09  5:24                                     ` Greg KH
2004-11-09  5:24                                       ` Greg KH
2004-11-09  5:24                                         ` Greg KH
2004-11-09  5:24                                           ` Greg KH
2004-11-09  5:24                                             ` Greg KH
2004-11-09  5:24                                               ` Greg KH
2004-11-09 10:17                 ` Jean Delvare
2004-11-09 11:12                   ` Arjan van de Ven
2004-11-09 14:10                     ` Jean Delvare
2004-11-09  9:29 ` [BK PATCH] " Jean Delvare
2004-11-09 15:21   ` 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=20041109152145.GB27269@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@Stimpy.netroedge.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