On Monday 28 August 2006 16:05, Arnd Bergmann wrote: > The patch below should address both these issues, as long as the libc > has a working implementation of syscall(2). I would prefer the _syscall() macros to stay independent of the actual glibc version. Or what do you do otherwise on a system with old glibc? Upgrading glibc is normally a major PITA. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- From: "H. Peter Anvin" <[email protected]>
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- From: "Horst H. von Brand" <[email protected]>
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- From: Adrian Bunk <[email protected]>
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- References:
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- From: Andi Kleen <[email protected]>
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- From: David Woodhouse <[email protected]>
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- From: Arnd Bergmann <[email protected]>
- Re: [PATCH 6/7] remove all remaining _syscallX macros
- Prev by Date: Re: [CFT:PATCH] Removing possible wrong asm/serial.h inclusions
- Next by Date: Re: [PATCH 1/3] kthread: update s390 cmm driver to use kthread
- Previous by thread: Re: [PATCH 6/7] remove all remaining _syscallX macros
- Next by thread: Re: [PATCH 6/7] remove all remaining _syscallX macros
- Index(es):
 |