From: Martin Pool <mbp@sourcefrog.net>
To: linux-ia64@vger.kernel.org
Subject: Re: kernel update (relative to 2.6.5)
Date: Wed, 14 Apr 2004 06:22:28 +0000 [thread overview]
Message-ID: <pan.2004.04.14.06.22.27.138621@sourcefrog.net> (raw)
In-Reply-To: <200404140103.i3E13cB0004406@napali.hpl.hp.com>
On Tue, 13 Apr 2004 18:03:38 -0700, David Mosberger wrote:
> At long last, the ia64-patch for 2.6.5...
> It's in the usual place:
>
> ftp://ftp.kernel.org/pub/linux/kernel/ports/ia64/v2.6/
>
> in file
>
> linux-2.6.5-ia64-040413.diff.gz
This seems to cause problems for me during make modules:
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/yellowfin.ko] has no C RC!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/tulip/winbond-840.ko] has no CRC!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/via-rhine.ko] has no C RC!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/typhoon.ko] has no CRC !
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/tulip/tulip.ko] has no CRC!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/tg3.ko] has no CRC!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/sundance.ko] has no CR C!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/starfire.ko] has no CR C!
*** Warning: "per_cpu__local_per_cpu_offset" [drivers/net/sk98lin/sk98lin.ko] ha s no CRC!
--
Martin
next prev parent reply other threads:[~2004-04-14 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 1:03 kernel update (relative to 2.6.5) David Mosberger
2004-04-14 6:22 ` Martin Pool [this message]
2004-04-14 7:14 ` Martin Pool
2004-04-14 11:59 ` Andreas Schwab
2004-04-15 2:54 ` Martin Pool
2004-04-15 5:11 ` David Mosberger
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=pan.2004.04.14.06.22.27.138621@sourcefrog.net \
--to=mbp@sourcefrog.net \
--cc=linux-ia64@vger.kernel.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