All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: Jean Delvare <khali@linux-fr.org>
Cc: sensors@Stimpy.netroedge.com, Deepak Saxena <dsaxena@plexity.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: checksum in (i2c) eeprom driver
Date: Thu, 19 May 2005 06:25:26 +0000	[thread overview]
Message-ID: <20041209231744.GA6446@kroah.com> (raw)
In-Reply-To: <vojkqBdx.1102603548.0379010.khali@localhost>

On Thu, Dec 09, 2004 at 03:45:48PM +0100, Jean Delvare wrote:
> 
> If the checksumming was that important, I guess it would have been the
> default, which it was not. If it is there for the sole purpose of
> allowing the user to prevent the eeprom driver from taking over
> non-eeprom chips, then the "ignore" module parameter can be used to
> achieve the same effect, faster, plus it is configurable on a
> per-address basis, while the checksum parameter isn't.

I agree, what's wrong with using the ignore stuff instead?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <greg@kroah.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: sensors@Stimpy.netroedge.com, Deepak Saxena <dsaxena@plexity.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: checksum in (i2c) eeprom driver
Date: Thu, 9 Dec 2004 15:17:44 -0800	[thread overview]
Message-ID: <20041209231744.GA6446@kroah.com> (raw)
In-Reply-To: <vojkqBdx.1102603548.0379010.khali@localhost>

On Thu, Dec 09, 2004 at 03:45:48PM +0100, Jean Delvare wrote:
> 
> If the checksumming was that important, I guess it would have been the
> default, which it was not. If it is there for the sole purpose of
> allowing the user to prevent the eeprom driver from taking over
> non-eeprom chips, then the "ignore" module parameter can be used to
> achieve the same effect, faster, plus it is configurable on a
> per-address basis, while the checksum parameter isn't.

I agree, what's wrong with using the ignore stuff instead?

thanks,

greg k-h

  reply	other threads:[~2005-05-19  6:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-09 12:53 checksum in (i2c) eeprom driver Jean Delvare
2005-05-19  6:25 ` Jean Delvare
2005-05-19  6:25 ` Mark Studebaker
2004-12-09 14:45   ` Jean Delvare
2005-05-19  6:25     ` Jean Delvare
2004-12-09 23:17     ` Greg KH [this message]
2005-05-19  6:25       ` Greg KH
2005-05-19  6:25 ` Mark Studebaker
2004-12-10  8:42   ` Jean Delvare
2005-05-19  6:25     ` Jean Delvare
2004-12-15  0:57     ` Mark M. Hoffman
2005-05-19  6:25       ` Mark M. Hoffman
2004-12-15  9:17       ` Jean Delvare
2005-05-19  6:25         ` Jean Delvare

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=20041209231744.GA6446@kroah.com \
    --to=greg@kroah.com \
    --cc=dsaxena@plexity.net \
    --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 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.