Messages in this thread | | | From | Andi Kleen <> | Subject | Re: build fix for x86_64... | Date | Fri, 20 Jul 2007 19:25:11 +0200 |
| |
On Friday 20 July 2007 19:03, H. Peter Anvin wrote: > Luck, Tony wrote: > > Which is better. But if we unconditionally set this CONFIG variable, > > then the code in fs/quota.c will have to read: > > > > #if defined(CONFIG_COMPAT) && defined(CONFIG_COMPAT_FOR_U64_ALIGNMENT) > > > > We can keep it simpler if the Kconfig file does the conditional for us: > > > > config COMPAT_FOR_U64_ALIGNMENT > > def_bool y > > depends on COMPAT > > No, that would be bad. If compat_u64 is used to carry 32-bit ABIs
That doesn't help for any old interfaces, like the one here. For those still ifdefs are needed. Interfaces that use compat_u64 just use a normal #ifdef CONFIG_COMPAT.
Besides I have my doubts compat_u64 will be the solution to these worries. We have hundreds of people adding various interfaces to Linux and it's unlikely they all heard about it. So likely these cases will occur again and again.
-Andi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |