From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
linux-trace-devel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: linux-next: Tree for Oct 29
Date: Wed, 30 Oct 2019 10:55:53 +0000 [thread overview]
Message-ID: <20191030105553.GH25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <CADYN=9+aqqHVP8tKFFCTKi_zzSt=PW5JVyU2sdaThgrHpYSjzQ@mail.gmail.com>
Please trim your replies; there's no need to force everyone to page
through 500 lines of Stephen's email to get to the content of your
message.
On Wed, Oct 30, 2019 at 11:25:19AM +0100, Anders Roxell wrote:
> When I'm building an arm kernel with this .config [1], I can see this
> build error on next tag next-20191029 and next-20191030. Tag
> next-20191028 built fine.
>
>
> $ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -skj$(getconf
> _NPROCESSORS_ONLN) O=obj-arm-20191029 zImage
> arm-linux-gnueabi-ld: kernel/trace/trace_preemptirq.o: in function
> `trace_hardirqs_on':
> trace_preemptirq.c:(.text+0x2a0): undefined reference to `return_address'
> arm-linux-gnueabi-ld: trace_preemptirq.c:(.text+0x2dc): undefined
> reference to `return_address'
> arm-linux-gnueabi-ld: kernel/trace/trace_preemptirq.o: in function
> `trace_hardirqs_off':
> trace_preemptirq.c:(.text+0x468): undefined reference to `return_address'
> arm-linux-gnueabi-ld: trace_preemptirq.c:(.text+0x494): undefined
> reference to `return_address'
> arm-linux-gnueabi-ld: kernel/trace/trace_irqsoff.o: in function
> `start_critical_timings':
> trace_irqsoff.c:(.text+0x798): undefined reference to `return_address'
> arm-linux-gnueabi-ld:
> kernel/trace/trace_irqsoff.o:trace_irqsoff.c:(.text+0xed4): more
> undefined references to `return_address' follow
> make[1]: *** [/srv/src/kernel/next-testing/Makefile:1074: vmlinux] Error 1
> make[1]: Target 'zImage' not remade because of errors.
> make: *** [Makefile:179: sub-make] Error 2
> make: Target 'zImage' not remade because of errors.
Known problem with one of Ben Dooks patches, which was dropped very
quickly when Olof's builder spotted the issue... though it looks like
I didn't push it out. Ben doesn't seem to be responding about his
broken patch though...
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2019-10-30 10:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 7:07 linux-next: Tree for Oct 29 Stephen Rothwell
2019-10-29 15:14 ` linux-next: Tree for Oct 29 (thermal/qcom/) Randy Dunlap
2019-10-30 10:25 ` linux-next: Tree for Oct 29 Anders Roxell
2019-10-30 10:55 ` Russell King - ARM Linux admin [this message]
2019-10-30 11:21 ` Anders Roxell
-- strict thread matches above, loose matches on Subject: below --
2025-10-29 2:37 Stephen Rothwell
2024-10-29 5:54 Stephen Rothwell
2021-10-29 8:25 Stephen Rothwell
2020-10-29 4:55 Stephen Rothwell
2018-10-29 6:02 Stephen Rothwell
2014-10-29 4:17 Stephen Rothwell
2013-10-29 9:30 Stephen Rothwell
2012-10-29 3:46 Stephen Rothwell
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=20191030105553.GH25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=anders.roxell@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).