All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: arch/riscv//mm/init.c:65:37: error: 'FIXADDR_START' undeclared; did you mean 'XAS_RESTART'?
Date: Fri, 10 Jan 2020 19:53:05 +0800	[thread overview]
Message-ID: <202001101902.AcKfUDKr%lkp@intel.com> (raw)

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

Hi Paul,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   4a3033ef6e6bb4c566bd1d556de69b494d76976c
commit: 8eace9fb39605f0e201223fd34306ba3b53969b7 Merge branch 'next/misc2' into for-next
date:   7 weeks ago
config: riscv-randconfig-a001-20200110 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 8eace9fb39605f0e201223fd34306ba3b53969b7
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=riscv 

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

All errors (new ones prefixed by >>):

   arch/riscv//mm/init.c: In function 'print_vm_layout':
>> arch/riscv//mm/init.c:65:37: error: 'FIXADDR_START' undeclared (first use in this function); did you mean 'XAS_RESTART'?
     print_mlk("fixmap", (unsigned long)FIXADDR_START,
                                        ^~~~~~~~~~~~~
                                        XAS_RESTART
   arch/riscv//mm/init.c:65:37: note: each undeclared identifier is reported only once for each function it appears in
>> arch/riscv//mm/init.c:66:20: error: 'FIXADDR_TOP' undeclared (first use in this function); did you mean 'FIXADDR_START'?
        (unsigned long)FIXADDR_TOP);
                       ^~~~~~~~~~~
                       FIXADDR_START
>> arch/riscv//mm/init.c:67:37: error: 'PCI_IO_START' undeclared (first use in this function); did you mean 'RQF_IO_STAT'?
     print_mlm("pci io", (unsigned long)PCI_IO_START,
                                        ^~~~~~~~~~~~
                                        RQF_IO_STAT
>> arch/riscv//mm/init.c:68:20: error: 'PCI_IO_END' undeclared (first use in this function); did you mean 'PCI_IOBASE'?
        (unsigned long)PCI_IO_END);
                       ^~~~~~~~~~
                       PCI_IOBASE
>> arch/riscv//mm/init.c:69:38: error: 'VMEMMAP_START' undeclared (first use in this function); did you mean 'MEMMAP_EARLY'?
     print_mlm("vmemmap", (unsigned long)VMEMMAP_START,
                                         ^~~~~~~~~~~~~
                                         MEMMAP_EARLY
>> arch/riscv//mm/init.c:70:20: error: 'VMEMMAP_END' undeclared (first use in this function); did you mean 'MEMREMAP_ENC'?
        (unsigned long)VMEMMAP_END);
                       ^~~~~~~~~~~
                       MEMREMAP_ENC
>> arch/riscv//mm/init.c:72:20: error: 'VMALLOC_END' undeclared (first use in this function); did you mean 'VM_LOCKED'?
        (unsigned long)VMALLOC_END);
                       ^~~~~~~~~~~
                       VM_LOCKED

vim +65 arch/riscv//mm/init.c

2cc6c4a0da4ab1 Yash Shah 2019-11-18  61  
2cc6c4a0da4ab1 Yash Shah 2019-11-18  62  static void print_vm_layout(void)
2cc6c4a0da4ab1 Yash Shah 2019-11-18  63  {
2cc6c4a0da4ab1 Yash Shah 2019-11-18  64  	pr_notice("Virtual kernel memory layout:\n");
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @65  	print_mlk("fixmap", (unsigned long)FIXADDR_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @66  		  (unsigned long)FIXADDR_TOP);
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @67  	print_mlm("pci io", (unsigned long)PCI_IO_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @68  		  (unsigned long)PCI_IO_END);
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @69  	print_mlm("vmemmap", (unsigned long)VMEMMAP_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @70  		  (unsigned long)VMEMMAP_END);
2cc6c4a0da4ab1 Yash Shah 2019-11-18  71  	print_mlm("vmalloc", (unsigned long)VMALLOC_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @72  		  (unsigned long)VMALLOC_END);
2cc6c4a0da4ab1 Yash Shah 2019-11-18  73  	print_mlm("lowmem", (unsigned long)PAGE_OFFSET,
2cc6c4a0da4ab1 Yash Shah 2019-11-18  74  		  (unsigned long)high_memory);
2cc6c4a0da4ab1 Yash Shah 2019-11-18  75  }
2cc6c4a0da4ab1 Yash Shah 2019-11-18  76  #else
2cc6c4a0da4ab1 Yash Shah 2019-11-18  77  static void print_vm_layout(void) { }
2cc6c4a0da4ab1 Yash Shah 2019-11-18  78  #endif /* CONFIG_DEBUG_VM */
2cc6c4a0da4ab1 Yash Shah 2019-11-18  79  

:::::: The code at line 65 was first introduced by commit
:::::: 2cc6c4a0da4ab11537b2567952b59af71a90ef12 RISC-V: Add address map dumper

:::::: TO: Yash Shah <yash.shah@sifive.com>
:::::: CC: Paul Walmsley <paul.walmsley@sifive.com>

---
0-DAY kernel test infrastructure                 Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org Intel Corporation

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

WARNING: multiple messages have this Message-ID (diff)
From: kbuild test robot <lkp@intel.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: arch/riscv//mm/init.c:65:37: error: 'FIXADDR_START' undeclared; did you mean 'XAS_RESTART'?
Date: Fri, 10 Jan 2020 19:53:05 +0800	[thread overview]
Message-ID: <202001101902.AcKfUDKr%lkp@intel.com> (raw)

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

Hi Paul,

FYI, the error/warning still remains.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   4a3033ef6e6bb4c566bd1d556de69b494d76976c
commit: 8eace9fb39605f0e201223fd34306ba3b53969b7 Merge branch 'next/misc2' into for-next
date:   7 weeks ago
config: riscv-randconfig-a001-20200110 (attached as .config)
compiler: riscv64-linux-gcc (GCC) 7.5.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout 8eace9fb39605f0e201223fd34306ba3b53969b7
        # save the attached .config to linux build tree
        GCC_VERSION=7.5.0 make.cross ARCH=riscv 

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

All errors (new ones prefixed by >>):

   arch/riscv//mm/init.c: In function 'print_vm_layout':
>> arch/riscv//mm/init.c:65:37: error: 'FIXADDR_START' undeclared (first use in this function); did you mean 'XAS_RESTART'?
     print_mlk("fixmap", (unsigned long)FIXADDR_START,
                                        ^~~~~~~~~~~~~
                                        XAS_RESTART
   arch/riscv//mm/init.c:65:37: note: each undeclared identifier is reported only once for each function it appears in
>> arch/riscv//mm/init.c:66:20: error: 'FIXADDR_TOP' undeclared (first use in this function); did you mean 'FIXADDR_START'?
        (unsigned long)FIXADDR_TOP);
                       ^~~~~~~~~~~
                       FIXADDR_START
>> arch/riscv//mm/init.c:67:37: error: 'PCI_IO_START' undeclared (first use in this function); did you mean 'RQF_IO_STAT'?
     print_mlm("pci io", (unsigned long)PCI_IO_START,
                                        ^~~~~~~~~~~~
                                        RQF_IO_STAT
>> arch/riscv//mm/init.c:68:20: error: 'PCI_IO_END' undeclared (first use in this function); did you mean 'PCI_IOBASE'?
        (unsigned long)PCI_IO_END);
                       ^~~~~~~~~~
                       PCI_IOBASE
>> arch/riscv//mm/init.c:69:38: error: 'VMEMMAP_START' undeclared (first use in this function); did you mean 'MEMMAP_EARLY'?
     print_mlm("vmemmap", (unsigned long)VMEMMAP_START,
                                         ^~~~~~~~~~~~~
                                         MEMMAP_EARLY
>> arch/riscv//mm/init.c:70:20: error: 'VMEMMAP_END' undeclared (first use in this function); did you mean 'MEMREMAP_ENC'?
        (unsigned long)VMEMMAP_END);
                       ^~~~~~~~~~~
                       MEMREMAP_ENC
>> arch/riscv//mm/init.c:72:20: error: 'VMALLOC_END' undeclared (first use in this function); did you mean 'VM_LOCKED'?
        (unsigned long)VMALLOC_END);
                       ^~~~~~~~~~~
                       VM_LOCKED

vim +65 arch/riscv//mm/init.c

2cc6c4a0da4ab1 Yash Shah 2019-11-18  61  
2cc6c4a0da4ab1 Yash Shah 2019-11-18  62  static void print_vm_layout(void)
2cc6c4a0da4ab1 Yash Shah 2019-11-18  63  {
2cc6c4a0da4ab1 Yash Shah 2019-11-18  64  	pr_notice("Virtual kernel memory layout:\n");
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @65  	print_mlk("fixmap", (unsigned long)FIXADDR_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @66  		  (unsigned long)FIXADDR_TOP);
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @67  	print_mlm("pci io", (unsigned long)PCI_IO_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @68  		  (unsigned long)PCI_IO_END);
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @69  	print_mlm("vmemmap", (unsigned long)VMEMMAP_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @70  		  (unsigned long)VMEMMAP_END);
2cc6c4a0da4ab1 Yash Shah 2019-11-18  71  	print_mlm("vmalloc", (unsigned long)VMALLOC_START,
2cc6c4a0da4ab1 Yash Shah 2019-11-18 @72  		  (unsigned long)VMALLOC_END);
2cc6c4a0da4ab1 Yash Shah 2019-11-18  73  	print_mlm("lowmem", (unsigned long)PAGE_OFFSET,
2cc6c4a0da4ab1 Yash Shah 2019-11-18  74  		  (unsigned long)high_memory);
2cc6c4a0da4ab1 Yash Shah 2019-11-18  75  }
2cc6c4a0da4ab1 Yash Shah 2019-11-18  76  #else
2cc6c4a0da4ab1 Yash Shah 2019-11-18  77  static void print_vm_layout(void) { }
2cc6c4a0da4ab1 Yash Shah 2019-11-18  78  #endif /* CONFIG_DEBUG_VM */
2cc6c4a0da4ab1 Yash Shah 2019-11-18  79  

:::::: The code at line 65 was first introduced by commit
:::::: 2cc6c4a0da4ab11537b2567952b59af71a90ef12 RISC-V: Add address map dumper

:::::: TO: Yash Shah <yash.shah@sifive.com>
:::::: CC: Paul Walmsley <paul.walmsley@sifive.com>

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

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

             reply	other threads:[~2020-01-10 11:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 11:53 kbuild test robot [this message]
2020-01-10 11:53 ` arch/riscv//mm/init.c:65:37: error: 'FIXADDR_START' undeclared; did you mean 'XAS_RESTART'? kbuild test robot
  -- strict thread matches above, loose matches on Subject: below --
2020-02-07  5:38 kbuild test robot
2020-02-07  5:38 ` kbuild test robot

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=202001101902.AcKfUDKr%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.