Ok this turns out to be an issue triggered by CONFIG_UNUSED_SYMBOLS not being set in the configuration for ti-omap. Turns out this is required for properly formed ABI files. There is no obvious reason however we cannot cope with the form when this is not set. So will:
1) fix the abi-check parser to cope with the dodgy lines,
2) enable CONFIG_UNUSED_SYMBOLS for ti-omap, and
3) get CONFIG_UNUSED_SYMBOLS into the enforcer configuration.
Ok this turns out to be an issue triggered by CONFIG_ UNUSED_ SYMBOLS not being set in the configuration for ti-omap. Turns out this is required for properly formed ABI files. There is no obvious reason however we cannot cope with the form when this is not set. So will:
1) fix the abi-check parser to cope with the dodgy lines, UNUSED_ SYMBOLS for ti-omap, and UNUSED_ SYMBOLS into the enforcer configuration.
2) enable CONFIG_
3) get CONFIG_