From: Tom Rini <trini@kernel.crashing.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: James.Bottomley@HansenPartnership.com,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux-2.4.10-pre10
Date: Sun, 16 Sep 2001 21:03:14 -0700 [thread overview]
Message-ID: <20010916210314.C14279@cpe-24-221-152-185.az.sprintbbd.net> (raw)
In-Reply-To: <20010916191705.B14279@cpe-24-221-152-185.az.sprintbbd.net> <1077.1000695392@kao2.melbourne.sgi.com>
In-Reply-To: <1077.1000695392@kao2.melbourne.sgi.com>
On Mon, Sep 17, 2001 at 12:56:32PM +1000, Keith Owens wrote:
> 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
Well, I guess my question is, is this arch-specific or driver specific?
The lasi700 driver is hppa-only. The NCR_D700 doesn't have any restrictions.
James?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2001-09-17 4:03 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 ` Linux-2.4.10-pre10 Keith Owens
2001-09-17 4:03 ` Tom Rini [this message]
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=20010916210314.C14279@cpe-24-221-152-185.az.sprintbbd.net \
--to=trini@kernel.crashing.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=kaos@ocs.com.au \
--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).