From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean Delvare Subject: Re: I2C device board info Date: Sat, 18 Jul 2009 15:29:18 +0200 Message-ID: <20090718152918.09912dea@hyperion.delvare> References: <20090718105600.GA29887@n2100.arm.linux.org.uk> <20090718150803.68fea223@hyperion.delvare> <20090718131237.GB4120@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090718131237.GB4120-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org> Sender: linux-i2c-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Russell King - ARM Linux Cc: Sascha Hauer , Ben Dooks , linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-i2c@vger.kernel.org On Sat, 18 Jul 2009 14:12:37 +0100, Russell King - ARM Linux wrote: > On Sat, Jul 18, 2009 at 03:08:03PM +0200, Jean Delvare wrote: > > Note that this is not an isolated case, although this one is worse > > because I2C_BOARD_INFO() and .type do not agree on the chip name. But > > there are several redundant .type definitions in arch/arm/mach-* and > > one in arch/blackfin/mach-bf527. Time to fix them? > > That is my intention - I'm preparing patches for Realview and Versatile. > This will only leave the MX* series of platforms in arch/arm doing this, > which fall into Sascha's domain. OK, thank you. I'll send a patch for the blackfin ones then. -- Jean Delvare