[8020] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

Re: SCSI Makefile cleanup

daemon@ATHENA.MIT.EDU (willy@thepuffingroup.com)
Sun Feb 6 17:26:06 2000

Date:   Sun, 6 Feb 2000 17:21:25 -0500
From: willy@thepuffingroup.com
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Eric Youngdale <eric@andante.org>, linux-kbuild@torque.net,
	linux-kernel@vger.rutgers.edu, linux-scsi@vger.rutgers.edu
Message-ID: <20000206172125.C517@thepuffingroup.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <389DEB75.8AF0586@mandrakesoft.com>; from Jeff Garzik on Sun, Feb 06, 2000 at 04:45:25PM -0500

On Sun, Feb 06, 2000 at 04:45:25PM -0500, Jeff Garzik wrote:
> Alan Cox wrote:
> > 
> > >     I was kind of thinking that a better way of doing this is to use a
> > > special ELF section that contains the initializer.  Then hosts.c would just
> > 
> > That facility already exists and I believe Jeff Garzik has scsi on his
> > current hit list for it. So the order will matter real soon now.
> 
> Yep.  After I update a bunch of drivers there will be another initcall
> bombing run

OK, since you'll be hammering on the scsi drivers through the makefile
checking it all works, can I ask you to apply the Makefile patch first and
test the whole shebang?  I have tested it a little, but not a large chunk.

Any suggestions on which Makefile to tackle next?  I was planning on
romping through the rest of the drivers/ directory, maybe drivers/block
next.

-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu

home help back first fref pref prev next nref lref last post