From: Chris Quinn <chris.quinn@htec.ERASE-THIS.demon.co.uk>
To: videoapp@globo.com
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Unresolved symbol prefetch
Date: Tue, 29 Oct 2002 12:01:48 +0000 [thread overview]
Message-ID: <3DBE78AC.8070005@htec.ERASE-THIS.demon.co.uk> (raw)
In-Reply-To: 3DAE3AEE00055D2F@riosf06.globoi.com
try the Linux Cross-Reference for luck:
http://lxr.linux.no/ident?i=prefetch
- chris
videoapp@globo.com wrote:
> Hello,
>
> I'm currently developing a loadable kernel module. At home, where I have
> an older linux distribution using kernel 2.2.17, it works fine. When I tested
> it in newer kernel versions, insmod complained about a unresolved symbol:
> "prefetch".
> What am I missing? Do I need some #include or some #define, somewhere? I
> have already searched the internet after that, but was unable to find a
> solution. I would appreciate any help.
>
> Thanks in advance.
>
> ________________________________________
> A busca mais veloz e precisa da internet. Acesse agora: http://www.zoom.com.br.
>
>
>
>
> ------------------------------------------------------------------------
>
> Subject:
> Versão kernel
> From:
> videoapp@globo.com
> Date:
> Mon, 28 Oct 2002 22:14:40 -0200
> To:
> videoapp@globo.com
>
>
> Conectiva 2.2.17
>
> ________________________________________
> A busca mais veloz e precisa da internet. Acesse agora: http://www.zoom.com.br.
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2002-10-29 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 11:44 Unresolved symbol prefetch videoapp
2002-10-29 12:01 ` Chris Quinn [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=3DBE78AC.8070005@htec.ERASE-THIS.demon.co.uk \
--to=chris.quinn@htec.erase-this.demon.co.uk \
--cc=linux-c-programming@vger.kernel.org \
--cc=videoapp@globo.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;
as well as URLs for NNTP newsgroup(s).