Start off with just __ref -- we enalbe you to override, if you do that then you can define your own. The way you'd use this, if you do override, is define your own __ref and then use include_next. Signed-off-by: Luis R. Rodriguez <mcgrof@xxxxxxxxxx> --- tools/include/linux/init.h | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 tools/include/linux/init.h diff --git a/tools/include/linux/init.h b/tools/include/linux/init.h new file mode 100644 index 000000000000..6d970a360a05 --- /dev/null +++ b/tools/include/linux/init.h @@ -0,0 +1,9 @@ +#ifndef _TOOLS_LINUX_INIT_H +#define _TOOLS_LINUX_INIT_H + +/* this means you can add your own to fit you own userspace needs */ +#ifndef __ref +#define __ref +#endif + +#endif /* _TOOLS_LINUX_INIT_H */ -- 2.11.0 -- 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