From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Miles Lane <miles.lane@comcast.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6.0-test2-bk2 (linus' tree) -- arch/ppc/platforms/pmac_cpufreq.c:219: undefined reference to `cpufreq_frequency_table_verify'
Date: 04 Aug 2003 00:01:38 +0200 [thread overview]
Message-ID: <1059948097.602.1.camel@gaston> (raw)
In-Reply-To: <200308031456.11550.miles.lane@comcast.net>
On Sun, 2003-08-03 at 23:56, Miles Lane wrote:
> After patching arch/ppc/kernel/setup.c to include cpu.h,
> I got this error:
>
> LD .tmp_vmlinux1
> arch/ppc/platforms/built-in.o(.pmac.text+0x584c): In function
> `pmac_cpufreq_setup':
> arch/ppc/platforms/pmac_cpufreq.c:219: undefined reference to
> `cpufreq_frequency_table_verify'
> arch/ppc/platforms/built-in.o(.pmac.text+0x588c):arch/ppc/platforms/pmac_cpufreq.c:229:
> undefined reference to `cpufreq_frequency_table_target'
> arch/ppc/platforms/built-in.o(.pmac.text+0x5930):arch/ppc/platforms/pmac_cpufreq.c:254:
> undefined reference to `cpufreq_frequency_table_cpuinfo'
> make: *** [.tmp_vmlinux1] Error 1
That's some Kconfig not up-to-date yet. I'm sorting out various
missing pmac patches for Linus and will send them over next week,
including that. You basically need CPU_FREQ_TABLE for now.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-03 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 21:56 2.6.0-test2-bk2 (linus' tree) -- arch/ppc/platforms/pmac_cpufreq.c:219: undefined reference to `cpufreq_frequency_table_verify' Miles Lane
2003-08-03 22:01 ` Benjamin Herrenschmidt [this message]
2003-08-03 22:15 ` Miles Lane
2003-08-03 22:17 ` Miles Lane
2003-08-04 11:34 ` Paul Mackerras
2003-08-04 15:26 ` Larry McVoy
2003-08-04 15:39 ` Michel Dänzer
2003-08-04 15:41 ` Larry McVoy
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=1059948097.602.1.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=miles.lane@comcast.net \
/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).