From: Keith Owens <kaos@ocs.com.au>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.10-pre10
Date: Mon, 17 Sep 2001 12:56:32 +1000 [thread overview]
Message-ID: <1077.1000695392@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Sun, 16 Sep 2001 19:17:05 MST." <20010916191705.B14279@cpe-24-221-152-185.az.sprintbbd.net>
On Sun, 16 Sep 2001 19:17:05 -0700,
Tom Rini <trini@kernel.crashing.org> wrote:
>I just posted this to the maintainer and linux-scsi, but is there any
>reason not do do this with either a CONFIG option or
>#ifdef CONFIG_SCSI_DRIVER_OR_ARCH_DOES_MEM_MAP
>#define MEM_MAPPED
>#endif
>
>53c700-mem.c is 53c700.c + a warning about being autogenerated +
>#define MEM_MAPPED
Kernel build works best if the source and object have the same name.
Generating two objects with different names from the same source is
awkward, it is even worse for kbuild 2.5. The obvious solution of
53c700-mem.c:
#define MEM_MAPPED
#include "53c700.c"
does not work correctly with current kbuild due to mkdep restrictions.
It does work with kbuild 2.5 and is exactly what I have done.
next prev parent reply other threads:[~2001-09-17 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-16 22:00 Linux-2.4.10-pre10 Linus Torvalds
2001-09-17 1:15 ` Linux-2.4.10-pre10 Keith Owens
2001-09-17 2:17 ` Linux-2.4.10-pre10 Tom Rini
2001-09-17 2:56 ` Keith Owens [this message]
2001-09-17 4:03 ` Linux-2.4.10-pre10 Tom Rini
2001-09-17 5:01 ` Linux-2.4.10-pre10 James Bottomley
2001-09-17 22:20 ` Linux-2.4.10-pre10 Andreas Steinmetz
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=1077.1000695392@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trini@kernel.crashing.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).