Hi, On Sun, 29 Jun 2008, Sam Ravnborg wrote: > Sample (first line is with unmodifed kconfig): > > -CONFIG_RADIO_ZOLTRIX_PORT=0x20c > +CONFIG_RADIO_ZOLTRIX_PORT=20c > > I guess this has something to do with the way we > represent a hex value internally. But I have not yet > dived into it. > > Can you see where it goes wrong? It's not really wrong, it's a valid value there. Only if it's saved like this in the header file, it would be wrong. I noticed that during testing too, that value is coming liking that directly from the Kconfig file. The real fix would be to deprecate hex values without prefix and automatically adding the prefix where needed (currently loading of Kconfig/.config). I though about making it more consistent, but it's not really a pressing issue, so I left it as is for now. bye, Roman -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
