Linux-Next Archive on
 help / color / Atom feed
From: Russell King - ARM Linux admin <>
To: Anders Roxell <>
Cc: Stephen Rothwell <>,
	Linux Next Mailing List <>,,
	Linux Kernel Mailing List <>,
	Linux ARM <>
Subject: Re: linux-next: Tree for Oct 29
Date: Wed, 30 Oct 2019 10:55:53 +0000
Message-ID: <> (raw)
In-Reply-To: <>

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

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:
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to 11.9Mbps down 500kbps up

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29  7:07 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 --
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 publically 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 \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Next Archive on

Archives are clonable:
	git clone --mirror linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ \
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone