From: Mark Rutland <mark.rutland@arm.com>
To: kbuild test robot <lkp@intel.com>
Cc: Torsten Duwe <duwe@lst.de>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: arch/arm64/kernel/entry-ftrace.S:238: undefined reference to `ftrace_graph_caller'
Date: Fri, 6 Dec 2019 12:41:29 +0000 [thread overview]
Message-ID: <20191206124129.GA21671@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <201912061533.I9JjEoWz%lkp@intel.com>
On Fri, Dec 06, 2019 at 03:08:40PM +0800, kbuild test robot wrote:
> Hi Torsten,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: b0d4beaa5a4b7d31070c41c2e50740304a3f1138
> commit: 3b23e4991fb66f6d152f9055ede271a726ef9f21 arm64: implement ftrace with regs
> All errors (new ones prefixed by >>):
>
> arch/arm64/kernel/entry-ftrace.o: In function `skip_ftrace_call':
> >> arch/arm64/kernel/entry-ftrace.S:238: undefined reference to `ftrace_graph_caller'
> arch/arm64/kernel/entry-ftrace.S:238:(.text+0x3c): relocation truncated to fit: R_AARCH64_CONDBR19 against undefined symbol `ftrace_graph_caller'
> arch/arm64/kernel/entry-ftrace.S:243: undefined reference to `ftrace_graph_caller'
> arch/arm64/kernel/entry-ftrace.S:243:(.text+0x54): relocation truncated to fit: R_AARCH64_CONDBR19 against undefined symbol `ftrace_graph_caller'
This is my bad; I messed up the ifdeffery so that ftrace_graph_caller
isn't defined for CONFIG_DYNAMIC_FTRACE && CONFIG_FUNCTION_GRAPH_TRACER.
I will send a patch shortly. Sorry about this.
Mark.
prev parent reply other threads:[~2019-12-06 12:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 7:08 kbuild test robot
2019-12-06 12:41 ` Mark Rutland [this message]
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=20191206124129.GA21671@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=amit.kachhap@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=duwe@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
/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
all inboxes | Powered by JetHome®