All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH RFC 3/4] kernel/resource: Make ioport_resource.start configurable
Date: Sat, 16 Jan 2021 08:37:50 +0800	[thread overview]
Message-ID: <202101160804.OMMa50O6-lkp@intel.com> (raw)
In-Reply-To: <1610729929-188490-4-git-send-email-john.garry@huawei.com>

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

Hi John,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on asm-generic/master soc/for-next linus/master v5.11-rc3 next-20210115]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]

url:    https://github.com/0day-ci/linux/commits/John-Garry/Fix-arm64-crash-for-accessing-unmapped-IO-port-regions-reboot/20210116-010800
base:   https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
config: parisc-randconfig-r022-20210115 (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/48d619e4d6beb0d7a086cbe60a0b24355d3ddd52
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review John-Garry/Fix-arm64-crash-for-accessing-unmapped-IO-port-regions-reboot/20210116-010800
        git checkout 48d619e4d6beb0d7a086cbe60a0b24355d3ddd52
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc 

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

All errors (new ones prefixed by >>):

>> kernel/resource.c:32:11: error: 'IO_SPACE_BASE' undeclared here (not in a function); did you mean 'QIF_SPACE_B'?
      32 |  .start = IO_SPACE_BASE,
         |           ^~~~~~~~~~~~~
         |           QIF_SPACE_B


vim +32 kernel/resource.c

    28	
    29	
    30	struct resource ioport_resource = {
    31		.name	= "PCI IO",
  > 32		.start	= IO_SPACE_BASE,
    33		.end	= IO_SPACE_LIMIT,
    34		.flags	= IORESOURCE_IO,
    35	};
    36	EXPORT_SYMBOL(ioport_resource);
    37	

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

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

  reply	other threads:[~2021-01-16  0:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 16:58 [PATCH RFC 0/4] Fix arm64 crash for accessing unmapped IO port regions (reboot) John Garry
2021-01-15 16:58 ` John Garry
2021-01-15 16:58 ` [PATCH RFC 1/4] arm64: io: Introduce IO_SPACE_BASE John Garry
2021-01-15 16:58   ` John Garry
2021-01-15 16:58 ` [PATCH RFC 2/4] asm-generic/io.h: Add IO_SPACE_BASE John Garry
2021-01-15 16:58   ` John Garry
2021-01-15 16:58 ` [PATCH RFC 3/4] kernel/resource: Make ioport_resource.start configurable John Garry
2021-01-15 16:58   ` John Garry
2021-01-16  0:37   ` kernel test robot [this message]
2021-01-15 16:58 ` [PATCH RFC 4/4] logic_pio: Warn on and discard accesses to addresses below IO_SPACE_BASE John Garry
2021-01-15 16:58   ` John Garry
2021-01-15 19:16   ` kernel test robot
2021-01-15 19:43   ` kernel test robot
2021-01-18  1:59 ` [PATCH RFC 0/4] Fix arm64 crash for accessing unmapped IO port regions (reboot) Jiaxun Yang
2021-01-18  1:59   ` Jiaxun Yang
2021-01-18  9:42   ` John Garry
2021-01-18  9:42     ` John Garry
2021-01-26 15:16 ` Arnd Bergmann
2021-01-26 15:16   ` Arnd Bergmann
2021-01-26 17:56   ` John Garry
2021-01-26 17:56     ` John Garry

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=202101160804.OMMa50O6-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.