linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* i2c_probe() vs i2c_detect()
@ 2003-04-03  1:23 Greg KH
  2003-04-04 13:33 ` Christoph Hellwig
  0 siblings, 1 reply; 2+ messages in thread
From: Greg KH @ 2003-04-03  1:23 UTC (permalink / raw)
  To: linux-kernel, sensors

Hi all,

Can anyone tell me why both i2c_probe() and i2c_detect() are in the
kernel at the same time?  They both almost do the same thing, with the
exception being i2c_detect() can handle i2c devices on the isa bus.

It kind of looks like the older i2c code and drivers used the
i2c_probe() call, while the lm_sensors code used i2c_detect().

If there are no objections, I'll merge the two of them, cutting about 2k
out of the kernel :)

thanks,

greg k-h

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: i2c_probe() vs i2c_detect()
  2003-04-03  1:23 i2c_probe() vs i2c_detect() Greg KH
@ 2003-04-04 13:33 ` Christoph Hellwig
  0 siblings, 0 replies; 2+ messages in thread
From: Christoph Hellwig @ 2003-04-04 13:33 UTC (permalink / raw)
  To: Greg KH; +Cc: linux-kernel, sensors

On Wed, Apr 02, 2003 at 05:23:07PM -0800, Greg KH wrote:
> Hi all,
> 
> Can anyone tell me why both i2c_probe() and i2c_detect() are in the
> kernel at the same time?  They both almost do the same thing, with the
> exception being i2c_detect() can handle i2c devices on the isa bus.
> 
> It kind of looks like the older i2c code and drivers used the
> i2c_probe() call, while the lm_sensors code used i2c_detect().
> 
> If there are no objections, I'll merge the two of them, cutting about 2k
> out of the kernel :)

Once ou're at it you could also try to get rid of the check_region abuse
in there :)


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-04-04 13:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-03  1:23 i2c_probe() vs i2c_detect() Greg KH
2003-04-04 13:33 ` Christoph Hellwig

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).