From: Jes Sorensen <jes@sunsite.dk>
To: Keith Owens <kaos@ocs.com.au>
Cc: sparclinux@vger.kernel.org, linux-m68k@lists.linux-m68k.org,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] SCSI in arch/{m68k,parisc,sparc*}/config.in
Date: 22 Jun 2001 15:18:57 +0200 [thread overview]
Message-ID: <d3ofrgbqke.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Keith Owens's message of "Fri, 22 Jun 2001 23:00:03 +1000"
>>>>> "Keith" == Keith Owens <kaos@ocs.com.au> writes:
Keith> cc: kaos@ocs.com.au please, I am not on these lists.
Keith> arch/{m68k,parisc,sparc*}/config.in have their own SCSI list
Keith> instead of using drivers/scsi/Config.in. Cleaning up the SCSI
Keith> config file is on my 2.5 TODO list, can you tell me why these
Keith> architectures have their own list of SCSI devices?
Keith> If it is because only some SCSI drivers work on these
Keith> architectures, do you really need to be this specific? Other
Keith> architectures source drivers/scsi/Config.in without checking
Keith> for arch dependent drivers. If the need is to support extra
Keith> arch specific drivers, use the same technique as acorn :-
For the m68k it's because we do not support any PCI/ISA devices and
all the SCSI drivers in drivers/scsi/Config.in at least used to not be
protected by CONFIG_ISA, CONFIG_PCI etc. hence we would end up with
200 questions about SCSI drivers that do not work. If you can convince
Linus to take a patch that puts CONFIG_{ISA,PCI,SBUS,NUBUS,ZORRO} in
drivers/scsi/Config.in then we can move it no problem.
Jes
next prev parent reply other threads:[~2001-06-22 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 13:00 [parisc-linux] SCSI in arch/{m68k,parisc,sparc*}/config.in Keith Owens
2001-06-22 13:18 ` Jes Sorensen [this message]
2001-06-22 13:22 ` [parisc-linux] " Geert Uytterhoeven
2001-06-23 0:32 ` David S. Miller
2001-06-23 0:56 ` Keith Owens
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=d3ofrgbqke.fsf@lxplus015.cern.ch \
--to=jes@sunsite.dk \
--cc=kaos@ocs.com.au \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=sparclinux@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