Le 05/11/2011 15:56, Wolfgang Denk a écrit : > Dear Albert ARIBAUD, > > In message<4eb543af.7010...@aribaud.net> you wrote: >> >>> Note that you will only get a warning if a _different_ value get's >>> defined (``warning: "VAR" redefined''). If both values are the same, >>> no warning will be raised. >> >> Hmm, correct. In order to catch the mach-type creeping back in >> mach-types.h, we'd need to define something like >> >> #define MACH_TYPE_JADECPU (2636) >> >> I'll post an ARM-global patch for this, but as it will obviously not be >> a bugfix, it'll wait until next merge window. > > Please save the effort. Waht would it be good for? As long as the > values are the same, it's OK anyway. And if they should be different, > we get a bunch of warnings.
Just wanted to make sure we know when the temporary MACH_TYPE addition in the config header becomes obsolete. But then, I can also run a grep on include/configs/*.h whenever mach-types.h is updated. > Best regards, > > Wolfgang Denk Amicalement, -- Albert. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
