From: Helge Deller <deller@gmx.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
linux-parisc@vger.kernel.org
Cc: Sven Schnelle <svens@stackframe.org>,
James.Bottomley@hansenpartnership.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
lkft-triage@lists.linaro.org
Subject: Re: parisc/unwind: call callback with toplevel address
Date: Fri, 1 Oct 2021 21:12:43 +0200 [thread overview]
Message-ID: <2ef5185a-9a0f-5ee0-23fc-37e0b1dd1099@gmx.de> (raw)
In-Reply-To: <CA+G9fYtsteSfwTQKV8o6VtBQDoz-+nwOf0s0X8BCkQHgAc6sdw@mail.gmail.com>
On 10/1/21 12:30, Naresh Kamboju wrote:
> Following build errors noticed while building Linux next 20211001
> with gcc-11 for parisc architecture.
>
> arch/parisc/kernel/stacktrace.c: In function 'dump_trace':
> arch/parisc/kernel/stacktrace.c:20:13: error: 'regs' undeclared (first
> use in this function)
> 20 | if (regs)
> | ^~~~
> arch/parisc/kernel/stacktrace.c:20:13: note: each undeclared
> identifier is reported only once for each function it appears in
> arch/parisc/kernel/stacktrace.c:21:22: error: implicit declaration of
> function 'fn' [-Werror=implicit-function-declaration]
> 21 | if (!fn(cookie, regs->iaoq[0]))
> | ^~
> arch/parisc/kernel/stacktrace.c:21:25: error: 'cookie' undeclared
> (first use in this function)
> 21 | if (!fn(cookie, regs->iaoq[0]))
> | ^~~~~~
> cc1: some warnings being treated as errors
> make[3]: *** [scripts/Makefile.build:288:
> arch/parisc/kernel/stacktrace.o] Error 1
>
> Build config:
> https://builds.tuxbuild.com/1ytbtyEg5SDSQgS2Oj9RsCM4ZmS/config
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
I've dropped that patch.
Thanks!
Helge
> meta data:
> -----------
> git_repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next
> git_sha: a25006a77348ba06c7bc96520d331cd9dd370715
> git_short_log: a25006a77348 (\"Add linux-next specific files for 20211001\")
> kconfig: defconfig
> kernel_version: 5.15.0-rc3
> target_arch: parisc
> toolchain: gcc-11
>
> steps to reproduce:
> https://builds.tuxbuild.com/1ytbtyEg5SDSQgS2Oj9RsCM4ZmS/tuxmake_reproducer.sh
>
> --
> Linaro LKFT
> https://lkft.linaro.org
>
next prev parent reply other threads:[~2021-10-01 19:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 10:30 parisc/unwind: call callback with toplevel address Naresh Kamboju
2021-10-01 19:12 ` Helge Deller [this message]
2021-10-07 9:09 ` ATI Rage XL cp
2021-10-08 8:44 ` cp
2021-10-25 12:08 ` cp
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=2ef5185a-9a0f-5ee0-23fc-37e0b1dd1099@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=sfr@canb.auug.org.au \
--cc=svens@stackframe.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.