From: Paul Jackson <pj@sgi.com>
To: David Ford <david+challenge-response@blue-labs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux/wrapper.h, where does it come from?
Date: Tue, 8 Jun 2004 15:10:08 -0700 [thread overview]
Message-ID: <20040608151008.75d01bf0.pj@sgi.com> (raw)
In-Reply-To: <40C6295B.10101@blue-labs.org>
> These two files include it. While compiling the qc-usb module, it's
> searching for this file.
Could it be they are looking for the Linux 2.4 header file
include/linux/wrapper.h, which contains in its entirety:
====================== begin snip ======================
#ifndef _WRAPPER_H_
#define _WRAPPER_H_
#define mem_map_reserve(p) set_bit(PG_reserved, &((p)->flags))
#define mem_map_unreserve(p) clear_bit(PG_reserved, &((p)->flags))
#endif /* _WRAPPER_H_ */
====================== end snip ======================
Without this, I don't see offhand how either of the files:
sound/oss/au1000.c
sound/oss/ite8172.c
could be compiled, as they seem to use these mem_map_[un]*reserve() macros.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-06-08 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 21:02 linux/wrapper.h, where does it come from? David Ford
2004-06-08 22:10 ` Paul Jackson [this message]
2004-06-08 22:22 ` Paul Jackson
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=20040608151008.75d01bf0.pj@sgi.com \
--to=pj@sgi.com \
--cc=david+challenge-response@blue-labs.org \
--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 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.