archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <>
To: Greg Kroah-Hartman <>,
	Sasha Levin <>
Cc: linux-stable <>,,
	Ananth N Mavinakayanahalli <>,
	Michael Ellerman <>,
	"Naveen N. Rao" <>,
	Sandipan Das <>
Subject: [stable-rc 5.4] powerpc/sstep: Fix incorrect return from analyze_instr()
Date: Mon, 1 Mar 2021 23:43:25 +0530	[thread overview]
Message-ID: <> (raw)

On stable rc 5.10 the ppc defconfig build failed due to below errors/warnings.

make --silent --keep-going --jobs=8
O=/home/tuxbuild/.cache/tuxmake/builds/1/tmp ARCH=powerpc
CROSS_COMPILE=powerpc64le-linux-gnu- 'CC=sccache
powerpc64le-linux-gnu-gcc' 'HOSTCC=sccache gcc'
arch/powerpc/lib/sstep.c: In function 'analyse_instr':
arch/powerpc/lib/sstep.c:1415:3: error: label 'unknown_opcode' used
but not defined
   goto unknown_opcode;
make[3]: *** [scripts/ arch/powerpc/lib/sstep.o] Error 1
make[3]: Target '__build' not remade because of errors.

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 podman --target-arch powerpc --toolchain gcc-9
--kconfig defconfig

Linaro LKFT

             reply	other threads:[~2021-03-01 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 18:13 Naresh Kamboju [this message]
2021-03-01 19:04 ` [stable-rc 5.4] powerpc/sstep: Fix incorrect return from analyze_instr() Greg Kroah-Hartman

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