archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <>
To: open list <>,
	linux-stable <>,, Sasha Levin <>,
	Greg Kroah-Hartman <>
Cc: Niklas Schnelle <>,
	Alexander Gordeev <>,, Halil Pasic <>
Subject: [s390] pci_irq.c:106: error: implicit declaration of function 'smp_cpu_get_cpu_address'
Date: Thu, 10 Dec 2020 20:48:09 +0530	[thread overview]
Message-ID: <> (raw)

While building S390 the following kernel warning / error noticed
on stable -rc 5.4 branch with gcc-8, gcc-9 and gcc-10 and defconfig

make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/6/tmp ARCH=s390
CROSS_COMPILE=s390x-linux-gnu- 'CC=sccache s390x-linux-gnu-gcc'
'HOSTCC=sccache gcc' vmlinux
arch/s390/pci/pci_irq.c: In function 'zpci_set_irq_affinity':
arch/s390/pci/pci_irq.c:106:17: error: implicit declaration of
function 'smp_cpu_get_cpu_address'
  106 |  int cpu_addr = smp_cpu_get_cpu_address(cpumask_first(dest));
      |                 ^~~~~~~~~~~~~~~~~~~~~~~

Reported-by: Naresh Kamboju <>

steps to reproduce:
# TuxMake is a command line tool and Python library that provides
# portable and repeatable Linux kernel builds across a variety of
# architectures, toolchains, kernel configurations, and make targets.
# TuxMake supports the concept of runtimes.
# See, for that to work it requires
# that you install podman or docker on your system.
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
# See for complete documentation.

tuxmake --runtime docker --target-arch s390 --toolchain gcc-9
--kconfig defconfig

    target_arch: s390
    toolchain: gcc-9
    git_short_log: 82a0751eb2d3 (\Linux 5.4.83-rc1\)
    git_describe: v5.4.82-55-g82a0751eb2d3
    kernel_version: 5.4.83-rc1

full build log link,

Linaro LKFT

                 reply	other threads:[~2020-12-10 15:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

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

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \ \ \

* 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).