Hi Rashmica,

[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.5 next-20160322]
[if your patch is applied to the wrong git tree, please drop us a note to help 
improving the system]

url:    
https://github.com/0day-ci/linux/commits/Rashmica-Gupta/powerpc-pagetable-Add-option-to-dump-the-linux-pagetables/20160322-060934
base:   https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-allyesconfig (attached as .config)
reproduce:
        wget 
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
 -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=powerpc 

All errors (new ones prefixed by >>):

   arch/powerpc/mm/dump_hashpagetable.c: In function 'walk_pte':
>> arch/powerpc/mm/dump_hashpagetable.c:363:18: error: '_PAGE_COMBO' undeclared 
>> (first use in this function)
      if (((pteval & _PAGE_COMBO) == _PAGE_COMBO) ||
                     ^
   arch/powerpc/mm/dump_hashpagetable.c:363:18: note: each undeclared 
identifier is reported only once for each function it appears in

vim +/_PAGE_COMBO +363 arch/powerpc/mm/dump_hashpagetable.c

   357                  if (addr < VMALLOC_END)
   358                          psize = mmu_vmalloc_psize;
   359                  else
   360                          psize = mmu_io_psize;
   361  
   362                  /* check for secret 4K mappings */
 > 363                  if (((pteval & _PAGE_COMBO) == _PAGE_COMBO) ||
   364                          ((pteval & _PAGE_4K_PFN) == _PAGE_4K_PFN))
   365                          psize = mmu_io_psize;
   366  

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

Attachment: .config.gz
Description: Binary data

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to