From: Mike Frysinger Date: Sat, 18 Jul 2009 14:56:18 -0400 Subject: [U-Boot] =?iso-8859-1?q?=5BRFC=5D=A0CONFIG_naming_convetion?= In-Reply-To: <20090718110338.GA30699@game.jcrosoft.org> References: <20090718110338.GA30699@game.jcrosoft.org> Message-ID: <200907181456.20670.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Saturday 18 July 2009 07:03:38 Jean-Christophe PLAGNIOL-VILLARD wrote: > Hi all, > > Currently we have a mess in the drivers CONFIG naming convention > as example on I2C we have > CONFIG_I2C_XXXXX > CONFIG_DRIVER_XXX_I2C > CONFIG_XXXX_I2C > CONFIG_SYS_I2C_XXXX > > I think it will good to have common and clean naming convention > so I'll propose we use this one > CONFIG_namespace_XXXXX > and > CONFIG_SYS_namespace_XXXXX > > so it will resutly for I2C to this > > CONFIG_I2C_XXXXX > CONFIG_SYS_I2C_XXXX > > and the Makefile and KConfig it will be easier to sort and read are there really any guidelines on what "CONFIG_SYS_" is for ? i havent really figured out what "_SYS_" is supposed to indicate, so the new proposed naming is just as confusing imo. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20090718/734999c1/attachment.pgp