mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrick Gefre <pfg@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: cngam@sgi.com, Matthew Wilcox <matthew@wil.cx>,
	Grant Grundler <iod00d@hp.com>,
	Jesse Barnes <jbarnes@engr.sgi.com>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org
Subject: Re: [PATCH] 2.6 SGI Altix I/O code reorganization
Date: Tue, 05 Oct 2004 14:35:40 -0500	[thread overview]
Message-ID: <4162F78C.9020606@sgi.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F0221C900@scsmsx401.amr.corp.intel.com>

Luck, Tony wrote:
>>Yes, after looking at Grant's review/suggestion, we found that we can 
>>actually just use raw_pci_ops.  This will work well for us.  We have 
>>incoorporated this change.  No changes in pci/pci.c needed.
> 
> 
> Good.  Let's try to make some forward progress here.  I'd like
> to see the patches broken into a sequence something like this:
> 
> 1) Add new interfaces to header files to support any new API
>    needed by new files
> 2) Create all the new files (plain copies of old files where
>    a move is involved).
> 3) Functional changes to copied files.
> 4) Whitespace cleanup of copied files.
> 5) Point Makefiles to new files
> 6) Delete all the old/unused files.
> 7) Delete any API in headers that were only used by old files.
> 
> We'll need to coordinate with some other maintainrs for
> drivers/pci/hotplug/Kconfig and drivers/scsi/qla1280.c,
> but I'm ok with running all the other parts through the
> ia64 tree.
> 
> This follows the usual guidelines of a sequence of steps where
> the system is buildable+usable at each stage.
> 

Tony,

It had been suggested that we submit this as new code - since it can't be transitioned to. And I 
thought that was what we had decided on - a 'kill' patch and an 'add' patch. I can remove any 
Lindent'ing of older files if you don't want that. I will take out the Kconfig mod. I believe 
Christoph is the maintainer of the qla driver (he was one of the reviewers).

-- Pat

  reply	other threads:[~2004-10-05 19:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 19:16 Luck, Tony
2004-10-05 19:35 ` Patrick Gefre [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-11 20:49 Luck, Tony
2004-10-07 17:06 Luck, Tony
2004-10-07 17:22 ` Jesse Barnes
2004-10-07 18:59 ` Jes Sorensen
2004-10-05 20:34 Luck, Tony
2004-10-06 15:32 ` Patrick Gefre
2004-10-06 18:57   ` Grant Grundler
2004-10-06 19:09     ` Colin Ngam
2004-10-06 19:54       ` Grant Grundler
2004-10-06 19:54         ` Colin Ngam
2004-10-06 20:10         ` Patrick Gefre
2004-10-06 20:44           ` Jesse Barnes
2004-10-07 15:02             ` Patrick Gefre
2004-10-07 16:52               ` Jesse Barnes
2004-10-06 20:27         ` Jesse Barnes
2004-10-06 20:21           ` Colin Ngam
2004-10-06 20:33           ` Matthew Wilcox
2004-10-06 20:48           ` Grant Grundler
2004-10-06 21:05             ` Matthew Wilcox
2004-10-06 20:55               ` Colin Ngam
2004-10-08 15:16                 ` Colin Ngam
2004-10-08 16:37                   ` Jesse Barnes
2004-10-09 22:20                   ` Grant Grundler
     [not found]                     ` <4169A508.84FB19C7@sgi.com>
2004-10-11 14:03                       ` Patrick Gefre
2004-10-08 22:37                 ` Colin Ngam
2004-10-05  5:13 Luck, Tony
2004-10-05 15:43 ` Jesse Barnes
2004-10-05 16:22   ` Grant Grundler
2004-10-05 17:45     ` Matthew Wilcox
2004-10-05 19:00       ` Colin Ngam
2004-10-05 19:10       ` Grant Grundler
2004-10-05 19:15         ` Matthew Wilcox
2004-10-05 18:20 ` Patrick Gefre
2004-10-05 18:34   ` Jesse Barnes
2004-10-04 21:57 Pat Gefre
2004-10-05 15:48 ` Christoph Hellwig
2004-10-05 18:26   ` Patrick Gefre
2004-10-05 23:30   ` Patrick Gefre
2004-10-05 15:50 ` Christoph Hellwig

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=4162F78C.9020606@sgi.com \
    --to=pfg@sgi.com \
    --cc=cngam@sgi.com \
    --cc=iod00d@hp.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=tony.luck@intel.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

Powered by JetHome