From: Christoph Hellwig <hch@infradead.org>
To: Pat Gefre <pfg@sgi.com>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code reorganization
Date: Fri, 06 Aug 2004 13:18:36 +0000 [thread overview]
Message-ID: <20040806141836.A9854@infradead.org> (raw)
In-Reply-To: <200408042014.i74KE8fD141211@fsgi900.americas.sgi.com>; from pfg@sgi.com on Wed, Aug 04, 2004 at 03:14:08PM -0500
On Wed, Aug 04, 2004 at 03:14:08PM -0500, Pat Gefre wrote:
> o added new hardware support
> o code cleanup (typedefs, include files, etc.)
> o simplified the directory structure (all files were arch/ia64/sn/io/
> are now under arch/ia64/sn/ioif/)
> o code size reduced by >50%
> o major reorg of the code itself
> o copyright updates
Yikes, this is truely horrible. First your patch ordering doesn't make
any sense, with just the first patch applied the system won't work at all.
Please submit a series of _small_ patches going from A to B keeping the code
working everywhere inbetween.
Your new directory structure is very bad. Just stick all files into
arch/ia64/sn/io/ instead of adding subdirectories for often just a single
file.
Now to the contents:
002-pci-fixups:
you're adding tons of non-standard SAL calls for who knows what. In
fact this pretty much looks like you're just moving the existing crappy
code into the prom so the bad Linux guys can't complain about it anymore.
Please switch to the standard ACPI PCI probing mechanism all other IA64
machines support and you can get rid of all that.
You're duplicating the kernel's PCI to PCI bridge support, with the normal
IA64 pci code it would just work..
003-pci-support:
The PCI DMA implementation is still ubercomplicated. See the PCI DMA code
I sent you long ago.
Of the code in pci_extensions.c only two are actually used in the kernel
(snia_pcibr_rrb_alloc and snia_pcidev_endian_set), please remove the unused
other ones.
004-pci-bridge_drivers:
You still have code dealing with all kinds of PCIIO_ and PCIBR_ flags
that will never be set through the Linux interfaces. Again see the DMA
mapping code I sent you.
006-bte:
Please merge bte_error.c into the existing bte.c
007-io-hub-provider:
tio_provider and hub_provider have exactly the same methods, no need to
keep the xtalk_provider_t abstraction at all
008-kdb-support-funtions:
kdb isn't in mainline, please add the two files to the kdb patch instead
next prev parent reply other threads:[~2004-08-06 13:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 20:14 Altix I/O code reorganization Pat Gefre
2004-08-05 0:31 ` Grant Grundler
2004-08-05 18:16 ` Greg KH
2004-08-05 20:51 ` Pat Gefre
2004-08-05 21:08 ` Greg KH
2004-08-05 21:32 ` Jesse Barnes
2004-08-05 21:36 ` Greg KH
2004-08-06 13:18 ` Christoph Hellwig [this message]
2004-08-06 16:19 ` Jesse Barnes
2004-08-07 10:58 ` Christoph Hellwig
2004-08-11 23:24 ` Patrick Gefre
2004-08-12 9:15 ` Christoph Hellwig
2004-08-12 14:47 ` Jesse Barnes
2004-08-12 15:21 ` Christoph Hellwig
2004-08-27 15:10 ` Latest Altix I/O code reorganization code Patrick Gefre
2004-08-27 15:14 ` Patrick Gefre
2004-08-27 15:21 ` Christoph Hellwig
2004-08-27 15:35 ` Patrick Gefre
2004-08-27 15:44 ` Christoph Hellwig
2004-08-27 15:23 ` Pat Gefre
2004-08-27 15:36 ` Christoph Hellwig
2004-08-27 15:45 ` Christoph Hellwig
2004-08-27 16:32 ` Patrick Gefre
2004-08-27 15:54 ` Christoph Hellwig
2004-08-27 16:06 ` Patrick Gefre
2004-08-27 16:21 ` Christoph Hellwig
2004-09-03 23:40 ` Christoph Hellwig
2004-09-07 22:10 ` Patrick Gefre
2004-09-07 22:16 ` Christoph Hellwig
2004-08-27 17:15 ` Christoph Hellwig
2004-08-29 6:39 ` Keith Owens
2004-08-29 7:16 ` Sam Ravnborg
2004-08-29 7:22 ` Keith Owens
2004-08-06 13:51 ` Altix I/O code reorganization Keith Owens
2004-08-06 13:55 ` Christoph Hellwig
2004-08-06 15:47 ` Russ Anderson
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=20040806141836.A9854@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pfg@sgi.com \
/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