From mboxrd@z Thu Jan 1 00:00:00 1970 From: khali@linux-fr.org (Jean Delvare) Date: Thu, 19 May 2005 06:25:26 +0000 Subject: checksum in (i2c) eeprom driver Message-Id: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-kernel@vger.kernel.org Cc: LM Sensors , Greg KH , Deepak Saxena 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261514AbULIMyA (ORCPT ); Thu, 9 Dec 2004 07:54:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261516AbULIMyA (ORCPT ); Thu, 9 Dec 2004 07:54:00 -0500 Received: from zone4.gcu-squad.org ([213.91.10.50]:250 "EHLO zone4.gcu-squad.org") by vger.kernel.org with ESMTP id S261514AbULIMx6 convert rfc822-to-8bit (ORCPT ); Thu, 9 Dec 2004 07:53:58 -0500 Date: Thu, 9 Dec 2004 13:53:04 +0100 (CET) To: linux-kernel@vger.kernel.org Subject: checksum in (i2c) eeprom driver X-IlohaMail-Blah: khali@localhost X-IlohaMail-Method: mail() [mem] X-IlohaMail-Dummy: moo X-Mailer: IlohaMail/0.8.13 (On: webmail.gcu.info) Message-ID: From: "Jean Delvare" Bounce-To: "Jean Delvare" CC: LM Sensors , Greg KH , Deepak Saxena MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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