[8021] in linux-scsi channel archive
Re: SCSI Makefile cleanup
daemon@ATHENA.MIT.EDU (Jeff Garzik)
Sun Feb 6 17:36:14 2000
Message-ID: <389DF6D3.5E528C59@mandrakesoft.com>
Date: Sun, 06 Feb 2000 17:33:55 -0500
From: Jeff Garzik <jgarzik@mandrakesoft.com>
MIME-Version: 1.0
To: willy@thepuffingroup.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
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
willy@thepuffingroup.com wrote:
> 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.
sure, though it probably won't be this week. please cc any updates in
the meantime to me...
> Any suggestions on which Makefile to tackle next? I was planning on
> romping through the rest of the drivers/ directory, maybe drivers/block
> next.
I already sent Linus a pending patch against 2.3.42 which converts
drivers/char, and drivers/net is already done. Unless there are
problems, I hope that will appear after the LinuxWorld dust settles on
Linus' desk. :) drivers/block would be good, though step lightly as
some of the dependencies in there have teeth, IIRC. :) And there are a
ton of sub-directories inside the major driver directories which are
worth evaluating.
Jeff
--
Jeff Garzik | Post-Linux-Expo TODO: Learn more
Building 1024 | French curse words from Pixel.
MandrakeSoft, Inc. |
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
