linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: kbuild-all@lists.01.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 3/4] mm: HUGE_VMAP arch query functions cleanup
Date: Tue, 14 Apr 2020 04:17:23 +0800	[thread overview]
Message-ID: <202004140429.UEW7A37I%lkp@intel.com> (raw)
In-Reply-To: <20200413125303.423864-4-npiggin@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3315 bytes --]

Hi Nicholas,

I love your patch! Yet something to improve:

[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on powerpc/next tip/x86/mm linus/master v5.7-rc1 next-20200413]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Nicholas-Piggin/huge-vmalloc-mappings/20200414-031028
base:   https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: i386-tinyconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   In file included from include/asm-generic/io.h:887:0,
                    from arch/x86/include/asm/io.h:375,
                    from arch/x86/include/asm/dma.h:13,
                    from include/linux/memblock.h:14,
                    from arch/x86/mm/ioremap.c:10:
   include/linux/vmalloc.h:94:44: error: unknown type name 'prprot_t'; did you mean 'pgprot_t'?
    static inline bool arch_vmap_pmd_supported(prprot_t prot) { return false; }
                                               ^~~~~~~~
                                               pgprot_t
>> arch/x86/mm/ioremap.c:463:6: error: redefinition of 'arch_vmap_p4d_supported'
    bool arch_vmap_p4d_supported(pgprot_t prot)
         ^~~~~~~~~~~~~~~~~~~~~~~
   In file included from include/asm-generic/io.h:887:0,
                    from arch/x86/include/asm/io.h:375,
                    from arch/x86/include/asm/dma.h:13,
                    from include/linux/memblock.h:14,
                    from arch/x86/mm/ioremap.c:10:
   include/linux/vmalloc.h:92:20: note: previous definition of 'arch_vmap_p4d_supported' was here
    static inline bool arch_vmap_p4d_supported(pgprot_t prot) { return false; }
                       ^~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/mm/ioremap.c:468:6: error: redefinition of 'arch_vmap_pud_supported'
    bool arch_vmap_pud_supported(pgprot_t prot)
         ^~~~~~~~~~~~~~~~~~~~~~~
   In file included from include/asm-generic/io.h:887:0,
                    from arch/x86/include/asm/io.h:375,
                    from arch/x86/include/asm/dma.h:13,
                    from include/linux/memblock.h:14,
                    from arch/x86/mm/ioremap.c:10:
   include/linux/vmalloc.h:93:20: note: previous definition of 'arch_vmap_pud_supported' was here
    static inline bool arch_vmap_pud_supported(pgprot_t prot) { return false; }
                       ^~~~~~~~~~~~~~~~~~~~~~~

vim +/arch_vmap_p4d_supported +463 arch/x86/mm/ioremap.c

   462	
 > 463	bool arch_vmap_p4d_supported(pgprot_t prot)
   464	{
   465		return 0;
   466	}
   467	
 > 468	bool arch_vmap_pud_supported(pgprot_t prot)
   469	{
   470	#ifdef CONFIG_X86_64
   471		return boot_cpu_has(X86_FEATURE_GBPAGES);
   472	#else
   473		return 0;
   474	#endif
   475	}
   476	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 7255 bytes --]

  reply	other threads:[~2020-04-13 20:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13 12:52 [PATCH v2 0/4] huge vmalloc mappings Nicholas Piggin
2020-04-13 12:53 ` [PATCH v2 1/4] mm/vmalloc: fix vmalloc_to_page for huge vmap mappings Nicholas Piggin
2020-04-13 13:34   ` Matthew Wilcox
2020-04-14 11:31     ` Nicholas Piggin
2020-04-13 12:53 ` [PATCH v2 2/4] mm: Move ioremap page table mapping function to mm/ Nicholas Piggin
2020-04-13 12:53 ` [PATCH v2 3/4] mm: HUGE_VMAP arch query functions cleanup Nicholas Piggin
2020-04-13 20:17   ` kbuild test robot [this message]
2020-04-13 20:29   ` kbuild test robot
2020-04-13 23:56   ` kbuild test robot
2020-04-13 23:56   ` [PATCH] mm: fix boolreturn.cocci warnings kbuild test robot
2020-04-13 12:53 ` [PATCH v2 4/4] mm/vmalloc: Hugepage vmalloc mappings Nicholas Piggin
2020-04-13 13:41   ` Matthew Wilcox
2020-04-14 11:39     ` Nicholas Piggin
2020-04-14 12:28     ` Christophe Leroy
2020-04-14 14:20       ` Matthew Wilcox
2020-04-14  7:23   ` Christoph Hellwig
2020-04-14 12:13     ` Nicholas Piggin
2020-04-14 13:02       ` Christoph Hellwig
2020-04-14 14:48         ` Nicholas Piggin
2020-04-15 10:47   ` Will Deacon
2020-04-16  2:38     ` Nicholas Piggin
2020-07-01  7:10   ` Zefan Li
2020-07-03  0:15     ` Nicholas Piggin
2020-07-20  2:02   ` Zefan Li
2020-07-20  2:49     ` Nicholas Piggin
2020-04-14  0:27 ` [PATCH v2 0/4] huge " David Rientjes
2020-04-14 12:23   ` Nicholas Piggin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202004140429.UEW7A37I%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).