On Mon, Sep 22, 2014 at 09:11:16AM -0700, Josh Triplett wrote: > @@ -3,7 +3,7 @@ > # > > mmu-y := nommu.o > -mmu-$(CONFIG_MMU) := fremap.o gup.o highmem.o madvise.o memory.o mincore.o \ > +mmu-$(CONFIG_MMU) := fremap.o gup.o highmem.o memory.o mincore.o \ > mlock.o mmap.o mprotect.o mremap.o msync.o rmap.o \ > vmalloc.o pagewalk.o pgtable-generic.o > > @@ -11,7 +11,7 @@ ifdef CONFIG_CROSS_MEMORY_ATTACH > mmu-$(CONFIG_MMU) += process_vm_access.o > endif > > -obj-y := filemap.o mempool.o oom_kill.o fadvise.o \ > +obj-y := filemap.o mempool.o oom_kill.o \ > maccess.o page_alloc.o page-writeback.o \ > readahead.o swap.o truncate.o vmscan.o shmem.o \ > util.o mmzone.o vmstat.o backing-dev.o \ > @@ -28,6 +28,9 @@ else > obj-y += bootmem.o > endif > > +ifdef CONFIG_MMU > + obj-$(CONFIG_ADVISE_SYSCALLS) += fadvise.o madvise.o > +endif That makes fadvise MMU-only, but I don't see why it should be. Was that intentional? -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
