From: Matthew Wilcox <willy@debian.org>
To: Erik Mouw <erik@harddisk-recovery.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Xose Vazquez Perez <xose@wanadoo.es>,
linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: two sym53c8xx.o modules
Date: Thu, 9 Oct 2003 13:38:57 +0100 [thread overview]
Message-ID: <20031009123857.GC27861@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20031009122428.GF11525@bitwizard.nl>
On Thu, Oct 09, 2003 at 02:24:28PM +0200, Erik Mouw wrote:
> No, it's not allright. Modprobe can't distinguish between
> sym53c8xx_2/sym53c8xx.o and sym53c8xx.o, you have to figure out the
> full path and insmod one of them manually. Xose is right in that
> sym53c8xx_2/sym53c8xx.o should be renamed in sym53c8xx_2/sym53c8xx_2.o.
> Compare with aic7xxx and aic7xxx_old.
Is it really important to change this at this stage of 2.4? For
reference, sym1 has already gone away in 2.6, so it'll be incovenient
for users no matter what you change. Let's stick with the devil we know.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-10-09 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 0:43 Xose Vazquez Perez
2003-10-09 11:41 ` Marcelo Tosatti
2003-10-09 12:24 ` Erik Mouw
2003-10-09 12:38 ` Matthew Wilcox [this message]
2003-10-09 13:11 ` Erik Mouw
2003-10-09 13:21 ` Matthew Wilcox
2003-10-09 14:04 ` Erik Mouw
2003-10-09 15:44 ` Xose Vazquez Perez
2003-10-09 13:00 ` Marcelo Tosatti
2003-10-09 16:05 ` Xose Vazquez Perez
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=20031009123857.GC27861@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=erik@harddisk-recovery.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=xose@wanadoo.es \
/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
Powered by JetHome