From: Tomas Szepe <szepe@pinerecords.com>
To: "David S. Miller" <davem@redhat.com>
Cc: zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: sparc32 sunrpc.o
Date: Sat, 28 Sep 2002 18:13:16 +0200 [thread overview]
Message-ID: <20020928161316.GA4323@louise.pinerecords.com> (raw)
In-Reply-To: <20020928122817.GV27082@louise.pinerecords.com>
> > From: Pete Zaitcev <zaitcev@redhat.com>
> > Date: Thu, 26 Sep 2002 17:27:24 -0400
> >
> > > Since 2.4.20-pre2 or 3, sunrpc.o has had this problem on sparc32:
> > >
> > > depmod: *** Unresolved symbols in /lib/modules/2.4.20-pre8/kernel/net/sunrpc/sunrpc.o
> > > depmod: ___illegal_use_of_BTFIXUP_SETHI_in_module
> > > depmod: ___f_set_pte
> > > depmod: fix_kmap_begin
> > > depmod: ___f_flush_cache_all
> > > depmod: ___f_pte_clear
> > > depmod: ___f_mk_pte
> > > depmod: ___f_flush_tlb_all
> >
> > Try these two things:
> >
> > No Peter, it really does use kmap_atomic stuff from modules, and this
> > precludes providing those routines inline in highmem.h, they must
> > live statically in main kernel image so that flush/pte calls can
> > be properly BTFIXUP'd.
> >
> > See my other email.
>
> Ok, DaveM, could you have a look at this patch?
Please disregard, highmem.c unreasonably included linux/highmem.h.
I'll be looking into this some more.
T.
next prev parent reply other threads:[~2002-09-28 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1033072381.13688.linux-kernel2news@redhat.com>
2002-09-26 21:27 ` Pete Zaitcev
2002-09-26 21:29 ` David S. Miller
2002-09-28 12:28 ` Tomas Szepe
2002-09-28 16:13 ` Tomas Szepe [this message]
2002-09-29 6:23 ` David S. Miller
2002-09-29 10:22 ` Tomas Szepe
2002-09-29 23:56 ` Pete Zaitcev
2002-09-30 0:50 ` David S. Miller
2002-09-30 2:05 ` Horst von Brand
2002-09-30 2:09 ` Tomas Szepe
2002-09-26 20:25 Tomas Szepe
2002-09-26 21:09 ` David S. Miller
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=20020928161316.GA4323@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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
all inboxes | Powered by JetHome®