linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Arnd Bergmann" <arnd@arndb.de>
To: "kernel test robot" <lkp@intel.com>,
	"Linus Walleij" <linus.walleij@linaro.org>
Cc: kbuild-all@lists.01.org,
	"Linux Memory Management List" <linux-mm@kvack.org>
Subject: Re: [linux-next:master 5820/6679] ERROR: modpost: "ioread64" [drivers/pci/switch/switchtec.ko] undefined!
Date: Mon, 12 Sep 2022 21:29:16 +0200	[thread overview]
Message-ID: <ef9237f7-89a4-4ddf-a096-d324f4640f16@www.fastmail.com> (raw)
In-Reply-To: <202209130203.tvgNPt7a-lkp@intel.com>

On Mon, Sep 12, 2022, at 8:24 PM, kernel test robot wrote:
> tree:   
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git 
> master
> head:   044b771be9c5de9d817dfafb829d2f049c71c3b4
> commit: 77bfc8bdb5a1cdbcea21daccdf1686e1bfea3db6 [5820/6679] parisc: 
> Remove 64bit access on 32bit machines
> config: parisc-buildonly-randconfig-r005-20220911 
> (https://download.01.org/0day-ci/archive/20220913/202209130203.tvgNPt7a-lkp@intel.com/config)
> compiler: hppa-linux-gcc (GCC) 12.1.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://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=77bfc8bdb5a1cdbcea21daccdf1686e1bfea3db6
>         git remote add linux-next 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>         git fetch --no-tags linux-next master
>         git checkout 77bfc8bdb5a1cdbcea21daccdf1686e1bfea3db6
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross 
> W=1 O=build_dir ARCH=parisc SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>, old ones prefixed by <<):
>
>>> ERROR: modpost: "ioread64" [drivers/pci/switch/switchtec.ko] undefined!


Applied this patch on top, thanks for the report!

     Arnd

commit fdc5bebfb66bf0d261818c2df2b01c2a005791fe
Author: Arnd Bergmann <arnd@arndb.de>
Date:   Mon Sep 12 21:27:19 2022 +0200

    parisc: hide ioread64 declaration on 32-bit
    
    The definition of ioread64 etc is hidden on 32-bit, but the declaration
    remained by accident, which led to the generic definition getting left
    out:
    
    ERROR: modpost: "ioread64" [drivers/pci/switch/switchtec.ko] undefined!
    
    Hide the declaration and #define under the same #ifdef.
    
    Reported-by: kernel test robot <lkp@intel.com>
    Fixes: 77bfc8bdb5a1 ("parisc: Remove 64bit access on 32bit machines")
    Signed-off-by: Arnd Bergmann <arnd@arndb.de>

diff --git a/arch/parisc/include/asm/io.h b/arch/parisc/include/asm/io.h
index 37580ad8d5bd..c05e781be2f5 100644
--- a/arch/parisc/include/asm/io.h
+++ b/arch/parisc/include/asm/io.h
@@ -227,6 +227,7 @@ extern void outsl (unsigned long port, const void *src, unsigned long count);
  * value for either 32 or 64 bit mode */
 #define F_EXTEND(x) ((unsigned long)((x) | (0xffffffff00000000ULL)))
 
+#ifdef CONFIG_64BIT
 #define ioread64 ioread64
 #define ioread64be ioread64be
 #define iowrite64 iowrite64
@@ -235,6 +236,7 @@ extern u64 ioread64(const void __iomem *addr);
 extern u64 ioread64be(const void __iomem *addr);
 extern void iowrite64(u64 val, void __iomem *addr);
 extern void iowrite64be(u64 val, void __iomem *addr);
+#endif
 
 #include <asm-generic/iomap.h>
 /*


      reply	other threads:[~2022-09-12 19:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 18:24 [linux-next:master 5820/6679] ERROR: modpost: "ioread64" [drivers/pci/switch/switchtec.ko] undefined! kernel test robot
2022-09-12 19:29 ` Arnd Bergmann [this message]

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=ef9237f7-89a4-4ddf-a096-d324f4640f16@www.fastmail.com \
    --to=arnd@arndb.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.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).