[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130610085715.GA6580@mudshark.cambridge.arm.com>
Date: Mon, 10 Jun 2013 09:57:16 +0100
From: Will Deacon <will.deacon@....com>
To: Chen Gang <gang.chen@...anux.com>
Cc: Marc Zyngier <Marc.Zyngier@....com>,
Catalin Marinas <Catalin.Marinas@....com>,
Santosh Shilimkar <santosh.shilimkar@...com>,
Tony Lindgren <tony@...mide.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH v2] arm64: kernel: compiling issue, need delete
read_current_timer().
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@...anux.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists