error with "pmem.c" compiling linux source code for android

I am compiling linux source code for android emulator. When i execute make command(for building and cross-compiling the linux source) i get the following error "pmem.c" file.

root@ubuntu:~/common# make
 CHK     include/linux/version.h
 CHK     include/linux/utsrelease.h
 SYMLINK include/asm -> include/asm-x86
 CALL    scripts/checksyscalls.sh
 CHK     include/linux/compile.h
 CC      drivers/misc/pmem.o
 drivers/misc/pmem.c:441: error: conflicting types for ‘phys_mem_access_prot’
 /home/preetam/common/arch/x86/include/asm/pgtable.h:383: note: previous declaration of         ‘phys_mem_access_prot’ was here
 drivers/misc/pmem.c: In function ‘flush_pmem_file’:
 drivers/misc/pmem.c:805: error: implicit declaration of function ‘dmac_flush_range’
 drivers/misc/pmem.c: In function ‘pmem_setup’:
 drivers/misc/pmem.c:1265: error: implicit declaration of function ‘ioremap_cached’
 drivers/misc/pmem.c:1266: warning: assignment makes pointer from integer without a cast
 make[2]: *** [drivers/misc/pmem.o] Error 1 
 make[1]: *** [drivers/misc] Error 2
 make: *** [drivers] Error 2
root@ubuntu:~/common# 

how to resolve this error. It seems that there may some problems in the "pmem.c" file and i'll have to choose different git repository. but that would be a very complex thing, as now i have already done most of the things till here. I might have to see correct version of this file. please someone tell what should i do?

开发者_StackOverflow中文版

how to solve this errors.

please help..thankyou!

---

There are several errors in the message you pasted, both conflicting types and implicit declarations. Three things that you might want to verify:

1. did you choose the correct processor architecture (ARCH) and cross compiler definition
2. does the chosen architecture mix in files from another arch (this is difficult to check, but you can start by checking the location of the files that are mentioned in the error message)
3. check these files themselves, to see it this is a bug (very unlikely, but you never know) and that you actually have to change some code