From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: kernel: compiling issue, need delete read_current_timer().
Date: Mon, 10 Jun 2013 09:57:16 +0100 [thread overview]
Message-ID: <20130610085715.GA6580@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <51B2B50A.1050305@asianux.com>
On Sat, Jun 08, 2013 at 05:37:30AM +0100, Chen Gang wrote:
> Hello Maintainers:
>
> Please help check it, when you have time.
[...]
> >> Under arm64, we will calibrate the delay loop statically using a known
> >> timer frequency, so delete read_current_timer(), or it will cause
> >> compiling issue with allmodconfig.
> >>
> >> The related error:
> >> ERROR: "read_current_timer" [lib/rbtree_test.ko] undefined!
> >> ERROR: "read_current_timer" [lib/interval_tree_test.ko] undefined!
> >> ERROR: "read_current_timer" [fs/ext4/ext4.ko] undefined!
> >> ERROR: "read_current_timer" [crypto/tcrypt.ko] undefined!
> >>
> >>
> >> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> >> ---
> >> arch/arm64/include/asm/timex.h | 6 +++---
> >> arch/arm64/kernel/time.c | 6 ------
> >> 2 files changed, 3 insertions(+), 9 deletions(-)
Looks ok to me. We'll take it for a spin and apply it if it doesn't catch
fire.
Will
next prev parent reply other threads:[~2013-06-10 8:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 6:48 [PATCH] arm64: kernel: compiling issue, need 'EXPORT_SYMBOL_GPL(read_current_timer)' Chen Gang
2013-05-20 7:15 ` Marc Zyngier
2013-05-20 9:56 ` Will Deacon
2013-05-21 4:06 ` Chen Gang
2013-05-21 6:13 ` Marc Zyngier
2013-05-21 8:41 ` Chen Gang
2013-05-21 8:58 ` Marc Zyngier
2013-05-21 9:26 ` Chen Gang
2013-05-21 8:53 ` Will Deacon
2013-05-21 9:27 ` Chen Gang
2013-05-21 9:46 ` [PATCH v2] arm64: kernel: compiling issue, need delete read_current_timer() Chen Gang
2013-05-27 10:02 ` Chen Gang
2013-06-08 4:37 ` Chen Gang
2013-06-10 8:57 ` Will Deacon [this message]
2013-06-13 1:12 ` Chen Gang
2013-06-10 8:57 ` Marc Zyngier
2013-06-13 1:13 ` Chen Gang
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=20130610085715.GA6580@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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).