From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262119AbTJIMjA (ORCPT ); Thu, 9 Oct 2003 08:39:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262118AbTJIMjA (ORCPT ); Thu, 9 Oct 2003 08:39:00 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:32218 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S262094AbTJIMi6 (ORCPT ); Thu, 9 Oct 2003 08:38:58 -0400 Date: Thu, 9 Oct 2003 13:38:57 +0100 From: Matthew Wilcox To: Erik Mouw Cc: Marcelo Tosatti , Xose Vazquez Perez , linux-scsi , linux-kernel Subject: Re: two sym53c8xx.o modules Message-ID: <20031009123857.GC27861@parcelfarce.linux.theplanet.co.uk> References: <3F84AF3C.9050408@wanadoo.es> <20031009122428.GF11525@bitwizard.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031009122428.GF11525@bitwizard.nl> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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