From: Matthew Wilcox <matthew@wil.cx>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: linux-scsi@vger.kernel.org
Subject: Re: can all 53c7xx-related stuff be removed?
Date: Sat, 9 Feb 2008 11:49:48 -0700 [thread overview]
Message-ID: <20080209184947.GC28967@parisc-linux.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0802091151440.5998@localhost.localdomain>
On Sat, Feb 09, 2008 at 11:54:43AM -0500, Robert P. J. Day wrote:
> just an observation that, even though 53c7xx content has been
> officially removed, there are still a few droppings hanging around the
> tree:
Erm. It's not just a driver, it's also the name of some chips.
> $ grep -r 53c7xx *
> arch/m68k/Makefile:# without -fno-strength-reduce the 53c7xx.c driver fails ;-(
Ask the m68k guys. Obviously, the comment can go away, but maybe they
want to remove -fno-strength-reduce now ...?
> Documentation/scsi/sym53c8xx_2.txt:by the 53c7xx and 53c8xx family.
> Documentation/scsi/ncr53c8xx.txt:by the 53c7xx and 53c8xx family.
> drivers/scsi/zalon.c: * Zalon 53c7xx device driver.
Here it's being used as the name of the chip.
> drivers/scsi/a4000t.c: * plus modifications of the 53c7xx.c driver to support the Amiga.
> drivers/scsi/zorro7xx.c: * plus modifications of the 53c7xx.c driver to support the Amiga.
This is part of the credit being given to Alan Hourihane. I don't see
how you can remove it.
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-02-09 18:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 16:54 can all 53c7xx-related stuff be removed? Robert P. J. Day
2008-02-09 18:49 ` Matthew Wilcox [this message]
2008-02-09 19:12 ` Robert P. J. Day
2008-02-09 19:32 ` Matthew Wilcox
2008-02-09 19:35 ` Robert P. J. Day
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=20080209184947.GC28967@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-scsi@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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