Searched hist:"2 f72d4f6a29cf84c40fc05c76020b347b4774393" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/arch/xtensa/kernel/ |
H A D | syscall.c | diff 2f72d4f6a29cf84c40fc05c76020b347b4774393 Tue Oct 23 22:17:05 CDT 2012 Chris Zankel <chris@zankel.net> xtensa: allow multi-inclusion for uapi/unistd.h
Xtensa implements a method that allows to generate a arbitrary output for each system call by defining the __SYSCALL(number, function, num_args). This usually requires to include uapi/unistd.h twice. Instead of removing the guard agains multiple inclusion entirely, allow to include unistd.h again only if __SYSCALL is defined. Note that __SYSCALL gets always undefined at the end of the file.
Signed-off-by: Chris Zankel <chris@zankel.net>
|
/openbmc/linux/arch/xtensa/include/uapi/asm/ |
H A D | unistd.h | diff 2f72d4f6a29cf84c40fc05c76020b347b4774393 Tue Oct 23 22:17:05 CDT 2012 Chris Zankel <chris@zankel.net> xtensa: allow multi-inclusion for uapi/unistd.h
Xtensa implements a method that allows to generate a arbitrary output for each system call by defining the __SYSCALL(number, function, num_args). This usually requires to include uapi/unistd.h twice. Instead of removing the guard agains multiple inclusion entirely, allow to include unistd.h again only if __SYSCALL is defined. Note that __SYSCALL gets always undefined at the end of the file.
Signed-off-by: Chris Zankel <chris@zankel.net>
|
/openbmc/linux/arch/xtensa/include/asm/ |
H A D | unistd.h | diff 2f72d4f6a29cf84c40fc05c76020b347b4774393 Tue Oct 23 22:17:05 CDT 2012 Chris Zankel <chris@zankel.net> xtensa: allow multi-inclusion for uapi/unistd.h
Xtensa implements a method that allows to generate a arbitrary output for each system call by defining the __SYSCALL(number, function, num_args). This usually requires to include uapi/unistd.h twice. Instead of removing the guard agains multiple inclusion entirely, allow to include unistd.h again only if __SYSCALL is defined. Note that __SYSCALL gets always undefined at the end of the file.
Signed-off-by: Chris Zankel <chris@zankel.net>
|