Changeset View
Changeset View
Standalone View
Standalone View
sys/modules/linuxkpi/Makefile
# $FreeBSD$ | # $FreeBSD$ | ||||
.PATH: ${SRCTOP}/sys/compat/linuxkpi/common/src | .PATH: ${SRCTOP}/sys/compat/linuxkpi/common/src | ||||
KMOD= linuxkpi | KMOD= linuxkpi | ||||
SRCS= linux_compat.c \ | SRCS= linux_compat.c \ | ||||
linux_current.c \ | linux_current.c \ | ||||
linux_dmi.c \ | linux_dmi.c \ | ||||
linux_hrtimer.c \ | linux_hrtimer.c \ | ||||
linux_idr.c \ | linux_idr.c \ | ||||
linux_kmod.c \ | linux_kmod.c \ | ||||
linux_kthread.c \ | linux_kthread.c \ | ||||
linux_kobject.c \ | |||||
bz: If we prefix the functions with linuxkpi or lkpi now, shouldn't we also call the files… | |||||
linux_lock.c \ | linux_lock.c \ | ||||
linux_page.c \ | linux_page.c \ | ||||
linux_pci.c \ | linux_pci.c \ | ||||
linux_radix.c \ | linux_radix.c \ | ||||
linux_rcu.c \ | linux_rcu.c \ | ||||
linux_seq_file.c \ | linux_seq_file.c \ | ||||
linux_schedule.c \ | linux_schedule.c \ | ||||
linux_shmemfs.c \ | linux_shmemfs.c \ | ||||
Show All 12 Lines |
If we prefix the functions with linuxkpi or lkpi now, shouldn't we also call the files linuxkpi_foo.c now for everything new we create?