public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Gefre <pfg@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Altix I/O code reorganization
Date: Wed, 11 Aug 2004 23:24:43 +0000	[thread overview]
Message-ID: <411AAABB.8070707@sgi.com> (raw)
In-Reply-To: <20040806141836.A9854@infradead.org>

I'm sending out a new patch set - the set of files will follow this email.

I'll add in this email the comments on the general comments and the comments on
the specific pach comments will be in the email for that updated patch - hopefully
that makes some kind of sense 8^). I didn't include the small bte change in this
set.


Christoph Hellwig wrote:
> On Wed, Aug 04, 2004 at 03:14:08PM -0500, Pat Gefre wrote:
> 
> 
> 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.
> 

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.

It is not practical to have small patches that will work independently.

The code base is now small enough that we should not have a problem
providing feedback.



> 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.
> 

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



  parent reply	other threads:[~2004-08-11 23:24 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
2004-08-06 16:19   ` Jesse Barnes
2004-08-07 10:58     ` Christoph Hellwig
2004-08-11 23:24   ` Patrick Gefre [this message]
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=411AAABB.8070707@sgi.com \
    --to=pfg@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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