All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Patrick Gefre <pfg@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code reorganization
Date: Thu, 12 Aug 2004 09:15:07 +0000	[thread overview]
Message-ID: <20040812101507.C5988@infradead.org> (raw)
In-Reply-To: <411AAABB.8070707@sgi.com>; from pfg@sgi.com on Wed, Aug 11, 2004 at 06:24:43PM -0500

On Wed, Aug 11, 2004 at 06:24:43PM -0500, Patrick Gefre wrote:
> This is a very BIG change.  However, the BIG change ends up with
> very little code in the kernel.  The reason is because, we have enhanced the
> functionalities in our Prom to actually configure and initialize all devices
> in the system instead of just the BaseIO devices.

Surely it can be spit out.  E.g. hwgraph removal is separate from your
SAL call stuff which is separate from dma mapping.

And,  let me repeat:

     There is absolutely _NO_ interest in adding yet another non-standard
     prom interface for PCI configuration.  IA64 has a standard ACPI-based
     interface that everyone but SGI implementent.  Please implement that one
     in your firmware.

> We do like our directory structures.  It provides very logical
> separation of code files.

You have more subdirectories than everything else in arch/ia64/ combined,
go figure. 


WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Patrick Gefre <pfg@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code reorganization
Date: Thu, 12 Aug 2004 10:15:07 +0100	[thread overview]
Message-ID: <20040812101507.C5988@infradead.org> (raw)
In-Reply-To: <411AAABB.8070707@sgi.com>; from pfg@sgi.com on Wed, Aug 11, 2004 at 06:24:43PM -0500

On Wed, Aug 11, 2004 at 06:24:43PM -0500, Patrick Gefre wrote:
> This is a very BIG change.  However, the BIG change ends up with
> very little code in the kernel.  The reason is because, we have enhanced the
> functionalities in our Prom to actually configure and initialize all devices
> in the system instead of just the BaseIO devices.

Surely it can be spit out.  E.g. hwgraph removal is separate from your
SAL call stuff which is separate from dma mapping.

And,  let me repeat:

     There is absolutely _NO_ interest in adding yet another non-standard
     prom interface for PCI configuration.  IA64 has a standard ACPI-based
     interface that everyone but SGI implementent.  Please implement that one
     in your firmware.

> We do like our directory structures.  It provides very logical
> separation of code files.

You have more subdirectories than everything else in arch/ia64/ combined,
go figure. 


  reply	other threads:[~2004-08-12  9:15 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 20:14 Altix I/O code reorganization Pat Gefre
2004-08-04 20:14 ` Pat Gefre
2004-08-05  0:31 ` Grant Grundler
2004-08-05  0:31   ` Grant Grundler
2004-08-05 18:16 ` Greg KH
2004-08-05 18:16   ` Greg KH
2004-08-05 20:51 ` Pat Gefre
2004-08-05 20:51   ` Pat Gefre
2004-08-05 21:08   ` Greg KH
2004-08-05 21:08     ` Greg KH
2004-08-05 21:32     ` Jesse Barnes
2004-08-05 21:32       ` Jesse Barnes
2004-08-05 21:36       ` Greg KH
2004-08-05 21:36         ` Greg KH
2004-08-06 13:18 ` Christoph Hellwig
2004-08-06 13:18   ` Christoph Hellwig
2004-08-06 16:19   ` Jesse Barnes
2004-08-06 16:19     ` Jesse Barnes
2004-08-07 10:58     ` Christoph Hellwig
2004-08-07 10:58       ` Christoph Hellwig
2004-08-11 23:24   ` Patrick Gefre
2004-08-11 23:24     ` Patrick Gefre
2004-08-12  9:15     ` Christoph Hellwig [this message]
2004-08-12  9:15       ` Christoph Hellwig
2004-08-12 14:47       ` Jesse Barnes
2004-08-12 14:47         ` Jesse Barnes
2004-08-12 15:21         ` Christoph Hellwig
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:10       ` Patrick Gefre
2004-08-27 15:14       ` Patrick Gefre
2004-08-27 15:14         ` Patrick Gefre
2004-08-27 15:21         ` Christoph Hellwig
2004-08-27 15:21           ` Christoph Hellwig
2004-08-27 15:35           ` Patrick Gefre
2004-08-27 15:35             ` Patrick Gefre
2004-08-27 15:44             ` Christoph Hellwig
2004-08-27 15:44               ` Christoph Hellwig
2004-09-03 23:12               ` Latest Altix I/O code rewrite Patrick Gefre
2004-08-27 15:23       ` Latest Altix I/O code reorganization code Pat Gefre
2004-08-27 15:23         ` Pat Gefre
2004-08-27 15:36       ` Christoph Hellwig
2004-08-27 15:36         ` Christoph Hellwig
2004-08-27 15:45       ` Christoph Hellwig
2004-08-27 15:45         ` Christoph Hellwig
2004-08-27 16:32         ` Patrick Gefre
2004-08-27 16:32           ` Patrick Gefre
2004-08-27 15:54       ` Christoph Hellwig
2004-08-27 15:54         ` Christoph Hellwig
2004-08-27 16:06         ` Patrick Gefre
2004-08-27 16:06           ` Patrick Gefre
2004-08-27 16:21         ` Christoph Hellwig
2004-08-27 16:21           ` Christoph Hellwig
2004-09-03 23:40           ` Christoph Hellwig
2004-09-03 23:40             ` Christoph Hellwig
2004-09-07 22:10             ` Patrick Gefre
2004-09-07 22:10               ` Patrick Gefre
2004-09-07 22:16               ` Christoph Hellwig
2004-09-07 22:16                 ` Christoph Hellwig
2004-08-27 17:15       ` Christoph Hellwig
2004-08-27 17:15         ` Christoph Hellwig
2004-08-29  6:39       ` Keith Owens
2004-08-29  6:39         ` Keith Owens
2004-08-29  7:16         ` Sam Ravnborg
2004-08-29  7:16           ` Sam Ravnborg
2004-08-29  7:22       ` Keith Owens
2004-08-29  7:22         ` Keith Owens
2004-08-06 13:51 ` Altix I/O code reorganization Keith Owens
2004-08-06 13:51   ` Keith Owens
2004-08-06 13:55   ` Christoph Hellwig
2004-08-06 13:55     ` Christoph Hellwig
2004-08-06 15:47 ` Russ Anderson
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=20040812101507.C5988@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.