public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kuppuswamy, Sathyanarayanan"  <sathyanarayanan.kuppuswamy@linux.intel.com>
To: kernel test robot <lkp@intel.com>, Andi Kleen <ak@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [intel-tdx:guest 37/107] lib/pci_iomap.c:30:9: error: implicit declaration of function 'ioremap_shared'; did you mean 'map_ioremap_shared'?
Date: Mon, 26 Jul 2021 14:20:18 -0700	[thread overview]
Message-ID: <75d49ee6-5731-a877-a0d4-5148fc0c2418@linux.intel.com> (raw)
In-Reply-To: <202107270426.vfFGcr89-lkp@intel.com>

Andi, Any comments on this issue? it looks like ioremap_shared is not redefined as ioremp
in some archs.

On 7/26/21 1:30 PM, kernel test robot wrote:
> tree:   https://github.com/intel/tdx.git guest
> head:   a81fb28d2e12ec7ee9667fbd8b08c7128d352f10
> commit: 9627c7de2c9fd39517b723ef9759e9579f25800c [37/107] pci: Add pci_iomap_shared{,_range}
> config: parisc-randconfig-r026-20210726 (attached as .config)
> compiler: hppa64-linux-gcc (GCC) 10.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/intel/tdx/commit/9627c7de2c9fd39517b723ef9759e9579f25800c
>          git remote add intel-tdx https://github.com/intel/tdx.git
>          git fetch --no-tags intel-tdx guest
>          git checkout 9627c7de2c9fd39517b723ef9759e9579f25800c
>          # save the attached .config to linux build tree
>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.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 error/warnings (new ones prefixed by >>):
> 
>     lib/pci_iomap.c: In function 'map_ioremap_shared':
>>> lib/pci_iomap.c:30:9: error: implicit declaration of function 'ioremap_shared'; did you mean 'map_ioremap_shared'? [-Werror=implicit-function-declaration]
>        30 |  return ioremap_shared(addr, size);
>           |         ^~~~~~~~~~~~~~
>           |         map_ioremap_shared
>>> lib/pci_iomap.c:30:9: warning: returning 'int' from a function with return type 'void *' makes pointer from integer without a cast [-Wint-conversion]
>        30 |  return ioremap_shared(addr, size);
>           |         ^~~~~~~~~~~~~~~~~~~~~~~~~~
>     cc1: some warnings being treated as errors
> 
> 
> vim +30 lib/pci_iomap.c
> 
>      27	
>      28	static void __iomem *map_ioremap_shared(phys_addr_t addr, size_t size)
>      29	{
>    > 30		return ioremap_shared(addr, size);
>      31	}
>      32	
> 
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
> 

-- 
Sathyanarayanan Kuppuswamy
Linux Kernel Developer

      reply	other threads:[~2021-07-26 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 20:30 [intel-tdx:guest 37/107] lib/pci_iomap.c:30:9: error: implicit declaration of function 'ioremap_shared'; did you mean 'map_ioremap_shared'? kernel test robot
2021-07-26 21:20 ` Kuppuswamy, Sathyanarayanan [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=75d49ee6-5731-a877-a0d4-5148fc0c2418@linux.intel.com \
    --to=sathyanarayanan.kuppuswamy@linux.intel.com \
    --cc=ak@linux.intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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