From: Miles Lane <miles.lane@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.21-bk25 -- agpgart_be.c:95:2: #error "Please define flush_cache."
Date: Sat, 2 Aug 2003 18:33:30 -0700 [thread overview]
Message-ID: <200308021833.30237.miles.lane@comcast.net> (raw)
make[4]: Entering directory `/home/usr/src/linux-2.4.21/drivers/char/agp'
gcc -D__KERNEL__ -I/home/usr/src/linux-2.4.21/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -I/home/usr/src/linux-2.4.21/arch/ppc -fsigned-char
-msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring
-nostdinc -iwithprefix include -DKBUILD_BASENAME=agpgart_be -DEXPORT_SYMTAB
-c agpgart_be.c
agpgart_be.c:95:2: #error "Please define flush_cache."
agpgart_be.c:401: warning: `agp_generic_agp_enable' defined but not used
agpgart_be.c:494: warning: `agp_generic_create_gatt_table' defined but not
used
agpgart_be.c:618: warning: `agp_generic_suspend' defined but not used
agpgart_be.c:623: warning: `agp_generic_resume' defined but not used
agpgart_be.c:628: warning: `agp_generic_free_gatt_table' defined but not used
agpgart_be.c:680: warning: `agp_generic_insert_memory' defined but not used
agpgart_be.c:742: warning: `agp_generic_remove_memory' defined but not used
agpgart_be.c:759: warning: `agp_generic_alloc_by_type' defined but not used
agpgart_be.c:764: warning: `agp_generic_free_by_type' defined but not used
agpgart_be.c:782: warning: `agp_generic_alloc_page' defined but not used
agpgart_be.c:802: warning: `agp_generic_destroy_page' defined but not used
make[4]: *** [agpgart_be.o] Error 1
next reply other threads:[~2003-08-03 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 1:33 Miles Lane [this message]
2003-08-03 1:38 ` 2.4.21-bk25 -- agpgart_be.c:95:2: #error "Please define flush_cache." Miles Lane
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=200308021833.30237.miles.lane@comcast.net \
--to=miles.lane@comcast.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).