summaryrefslogtreecommitdiff
path: root/board/bf533-ezkit
diff options
context:
space:
mode:
authorWolfgang Denk <wd@denx.de>2010-10-04 19:58:00 +0200
committerWolfgang Denk <wd@denx.de>2010-10-18 22:01:21 +0200
commitd24f2d321d8e78e990d100000d8efc4845c78b1c (patch)
tree3aefa485709092302434dbf442959b468b38ea64 /board/bf533-ezkit
parent9329cdfb3003a26bac1324fc05dbbbafc00dc37e (diff)
downloadu-boot-imx-d24f2d321d8e78e990d100000d8efc4845c78b1c.zip
u-boot-imx-d24f2d321d8e78e990d100000d8efc4845c78b1c.tar.gz
u-boot-imx-d24f2d321d8e78e990d100000d8efc4845c78b1c.tar.bz2
mkconfig: change CONFIG_MK_ prefix into plain CONFIG_
When planning for more generalization and Makefile cleanup it became obvious that the introduction of a separate CONFIG_MK_ name space for config options that were set through scripting in the Makefile was not a good idea. Originally the idea was to provide a script-free approach to supply configuration options - there was no real need for a separate name space. But when we now convert the existing Makefile entries to make use of this approach, it would mean that we have to touch a large number of board config files and add #ifdef / #define sequences to "convert" from the CONFIG_MK_ to the CONFIG_ name space. It seems much cleaner to get rid of this somewhat arbitrary _MK string now for the few boards that actually use it. Signed-off-by: Wolfgang Denk <wd@denx.de> Acked-by: Mike Frysinger <vapier@gentoo.org>
Diffstat (limited to 'board/bf533-ezkit')
0 files changed, 0 insertions, 0 deletions