From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] read_current_timer undefined
Date: Fri, 26 Oct 2012 12:15:34 +0100 [thread overview]
Message-ID: <20121026111534.GI20914@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1210261306370.20835@axis700.grange>
On Fri, Oct 26, 2012 at 12:09:18PM +0100, Guennadi Liakhovetski wrote:
> A recent commit
>
> commit 923df96b9f31b7d08d8438ff9677326d9537accf
> Author: Will Deacon <will.deacon@arm.com>
> Date: Fri Jul 6 15:46:45 2012 +0100
>
> ARM: 7451/1: arch timer: implement read_current_timer and get_cycles
>
> breaks linkage of modules, using get_cycles(), e.g.
>
> ERROR: "read_current_timer" [fs/ext4/ext4.ko] undefined!
>
> This is present in "next" of 23 October.
It's been present for a lot longer than that, but a fix has been merged into
mainline, so next should be ok now. See mainline commit f3accb122f2 ("ARM:
export default read_current_timer").
Will
prev parent reply other threads:[~2012-10-26 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 11:09 [BUG] read_current_timer undefined Guennadi Liakhovetski
2012-10-26 11:15 ` Will Deacon [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=20121026111534.GI20914@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).