Displaying 3 results from an estimated 3 matches for "init_utsnam".
Did you mean:
init_utsname
2008 Mar 31
2
alsa 1.016 compile error on latest kernel centos 5.1
...sa-project/alsa-driver-1.0.16/acore/info_oss.o
In file included
from /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/../alsa-kernel/core/info_oss.c:29,
from /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/info_oss.c:7:
include/linux/utsname.h:37:52: error: macro "init_utsname" passed 1
arguments, but takes just 0
In file included
from /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/../alsa-kernel/core/info_oss.c:29,
from /home/silentm/MessageNet/alsa-project/alsa-driver-1.0.16/acore/info_oss.c:7:
include/linux/utsname.h:38: error: expected ?=?, ?,?...
2007 Apr 18
4
[patch 0/4] Clean up asm/bugs.h, identify_cpu() and update COMPAT_VDSO
Hi Andi,
Four patches:
- clean up asm/bugs.h, by moving all the C code into its own C file
- split identify_cpu() into boot and secondary variants, so that
boot-time setup functions can be marked __init
- repost of the COMPAT_VDSO patches with a bit more robustness from
unknown DT_tags, and functions marked __init, since all this is
boot-time only setup.
Thanks,
J
--
2007 Apr 18
4
[patch 0/4] Clean up asm/bugs.h, identify_cpu() and update COMPAT_VDSO
Hi Andi,
Four patches:
- clean up asm/bugs.h, by moving all the C code into its own C file
- split identify_cpu() into boot and secondary variants, so that
boot-time setup functions can be marked __init
- repost of the COMPAT_VDSO patches with a bit more robustness from
unknown DT_tags, and functions marked __init, since all this is
boot-time only setup.
Thanks,
J
--