From: Ingo Molnar <mingo@elte.hu>
To: Rui Nuno Capela <rncbc@rncbc.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tsc_c3_compensate undefined since patch-2.6.13-rt13
Date: Tue, 4 Oct 2005 12:14:34 +0200 [thread overview]
Message-ID: <20051004101434.GA26882@elte.hu> (raw)
In-Reply-To: <43424B7C.9020508@rncbc.org>
* Rui Nuno Capela <rncbc@rncbc.org> wrote:
> Ingo,
>
> I'll take this late opportunity to report something that have been
> looking suspicious since 2.6.13-rt13, inclusive, about this symbol of
> tsc_c3_compensate being undefined and causing some noise on all kernel
> builds since then.
>
> To put things in brief, here follows a small exchange that took place
> on the linux-audio-user list, regarding this thingie. Apparently for
> Mark, it was a kernel build showstopper.
thanks for the reminder!
> WARNING:
> /lib/modules/2.6.13.1-rt13.0mdk/kernel/drivers/char/hangcheck-timer.ko
> needs unknown symbol do_monotonic_clock
> WARNING:
> /lib/modules/2.6.13.1-rt13.0mdk/kernel/drivers/acpi/processor.ko needs
> unknown symbol tsc_c3_compensate
back then i fixed do_monotonic_clock, but forgot to export
tsc_c3_compensate. I have fixed this in my tree, and have uploaded the
2.6.14-rc3-rt3 patch. Does it build without warnings for you now?
Ingo
next prev parent reply other threads:[~2005-10-04 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 7:24 [patch] drivers/ide/pci/alim15x3.c SMP fix Ingo Molnar
2005-09-01 8:13 ` Rui Nuno Capela
2005-09-01 8:17 ` Ingo Molnar
2005-09-01 8:51 ` Rui Nuno Capela
2005-09-01 10:42 ` Alan Cox
2005-10-03 6:50 ` Ingo Molnar
2005-10-03 16:24 ` Alan Cox
2005-10-04 9:29 ` tsc_c3_compensate undefined since patch-2.6.13-rt13 Rui Nuno Capela
2005-10-04 10:14 ` Ingo Molnar [this message]
2005-10-04 13:07 ` Rui Nuno Capela
2005-10-16 22:43 ` Rui Nuno Capela
2005-10-17 12:48 ` Ingo Molnar
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=20051004101434.GA26882@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=rncbc@rncbc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.