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


Hi all,

Any objection to me removing the checksumming code from the (i2c) eeprom
driver? Deepak had suggested we should do so a long time ago [1], and I
fully agree with his position. The checksum is application-specific and
verifying it doesn't belong to the kernel-space. The checksumming code
we (optionally) use at the moment only covers memory module EEPROMs as
far as I know, while EEPROMs exposed on I2C/SMBus may be of a variety of
other natures.

[1] http://archives.andrew.net.au/lm-sensors/msg21194.html

Thanks,
--
Jean Delvare

WARNING: multiple messages have this Message-ID (diff)
From: "Jean Delvare" <khali@linux-fr.org>
To: linux-kernel@vger.kernel.org
Cc: LM Sensors <sensors@stimpy.netroedge.com>,
	Greg KH <greg@kroah.com>, Deepak Saxena <dsaxena@plexity.net>
Subject: checksum in (i2c) eeprom driver
Date: Thu, 9 Dec 2004 13:53:04 +0100 (CET)	[thread overview]
Message-ID: <lNsWdTVB.1102596784.6279250.khali@localhost> (raw)


Hi all,

Any objection to me removing the checksumming code from the (i2c) eeprom
driver? Deepak had suggested we should do so a long time ago [1], and I
fully agree with his position. The checksum is application-specific and
verifying it doesn't belong to the kernel-space. The checksumming code
we (optionally) use at the moment only covers memory module EEPROMs as
far as I know, while EEPROMs exposed on I2C/SMBus may be of a variety of
other natures.

[1] http://archives.andrew.net.au/lm-sensors/msg21194.html

Thanks,
--
Jean Delvare

             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 Jean Delvare [this message]
2005-05-19  6:25 ` checksum in (i2c) eeprom driver Jean Delvare
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
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
2005-05-19  6:25       ` Greg KH

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=lNsWdTVB.1102596784.6279250.khali@localhost \
    --to=khali@linux-fr.org \
    --cc=dsaxena@plexity.net \
    --cc=greg@kroah.com \
    --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.