From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Subject: Re: Move eeprom drivers to drivers/misc/eeprom Date: Mon, 26 Jan 2009 23:55:27 -0800 Message-ID: <200901262355.27913.david-b@pacbell.net> References: <1232446982-7842-1-git-send-email-w.sang@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1232446982-7842-1-git-send-email-w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: spi-devel-general-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: Wolfram Sang Cc: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org, spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, rt2400-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Tuesday 20 January 2009, Wolfram Sang wrote: > This patch series carries out the proposal and while at it, moves an > eeprom driver which was already in drivers/misc to the new location. > > No code inside the drivers was changed and everything was > succesfully compile-tested. Now that thhis is in mainline ... I suggest two more changes: - at24 (i2c eeprom) doesn't need to be EXPERIMENTAL - we still need interfaces whereby kernel code can be given handles to the EEPROM devices, and then use them to read board config data out during boot. Obviously, the first one is easy. ;) - Dave ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword