public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Colin Ngam <cngam@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Pat Gefre <pfg@sgi.com>,
	akpm@osdl.org, davidm@napali.hpl.hp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Updating our sn code in 2.6
Date: Tue, 23 Dec 2003 08:46:11 -0600	[thread overview]
Message-ID: <3FE85533.E026DE86@sgi.com> (raw)
In-Reply-To: 20031223090227.A5027@infradead.org

Christoph Hellwig wrote:

> On Mon, Dec 22, 2003 at 08:55:10PM -0600, Pat Gefre wrote:
> > + Well, the pci-reorg patch is just wrong with tht remaining stuff
> > + and breaks the portable I/O code for IP27 and SN2 I'm working on.
> >
> > I have not heard any compelling reasons for keeping non-ia64, non-Altix
> > code in the ia64, Altix code base. The code re-org is aimed towards a
> > new ASIC we are working on - we feel it is needed.
>
> Again, you can reorganize code as much as you want.  Just don't change
> macro names randomly.  And the reason is once again that there will be
> a code drop supporting SN2 and IP27 in the same codebase soon, going
> the usual linux way of architecture-independant drivers for common hardware.

Hi Christoph,

You are ofcourse talking about linux/drivers/.. right?

IP27 is not a supported architecture under linux/arch/ia64/sn/io/..
The IP27 MIPS processor/io hardware(bridge/Xbridge)/BIOS for IP27 are very much
different than our SN2 product, supported within the linux/arch/ia64 tree -
ia64 processors, IO Chipsets(PIC, TIO(CP,CA)), and System BIOS.

Is that not supported under the linux/arch/mips tree?

Happy Holidays all.

colin

>
>
> > + issues before merging, it's not that much anyway..
> >
> > I think I did. I sent another email with the changes I made for the
> > issues you raised - and updated the patches. If I missed any, please
> > let me know.
>
> Ok, I haven't looked at that yet.
>
> > David or Andrew can you take these patches ?
>
> Please backpourt the renaming first.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2003-12-23 15:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-19  2:59 [PATCH] Updating our sn code in 2.6 Pat Gefre
2003-12-19 11:43 ` Christoph Hellwig
2003-12-20  0:35   ` Pat Gefre
2003-12-20  1:24     ` Jesse Barnes
2003-12-20  3:05       ` Jesse Barnes
2003-12-20 12:27         ` Christoph Hellwig
2003-12-23  2:55           ` Pat Gefre
2003-12-23  9:02             ` Christoph Hellwig
2003-12-23 14:46               ` Colin Ngam [this message]
2003-12-23 16:55                 ` Christoph Hellwig
2003-12-26 19:42                   ` Colin Ngam
2003-12-28 14:44                     ` Christoph Hellwig
2003-12-28 16:32                       ` Colin Ngam
2003-12-28 17:22                         ` Christoph Hellwig
2003-12-29  1:10                           ` Colin Ngam
2003-12-29  1:21                           ` Colin Ngam
2003-12-28 14:36             ` Christoph Hellwig
2003-12-29 23:41               ` Jesse Barnes
2003-12-30 21:21               ` Pat Gefre
2003-12-30 21:24                 ` Christoph Hellwig
2004-01-02 19:47                   ` Patrick Gefre
2004-01-02 20:11                     ` Christoph Hellwig
2004-03-29 15:39                     ` Christoph Hellwig
2004-03-29 15:39                   ` Patrick Gefre
  -- strict thread matches above, loose matches on Subject: below --
2003-11-06 23:31 Pat Gefre
2003-11-07 10:25 ` Christoph Hellwig
2003-11-13  0:26   ` Pat Gefre
2003-11-13  2:42     ` Paul Jackson
2003-11-13  6:58     ` Christoph Hellwig
2003-11-13 16:48       ` Jesse Barnes
2003-11-14 12:10         ` 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=3FE85533.E026DE86@sgi.com \
    --to=cngam@sgi.com \
    --cc=akpm@osdl.org \
    --cc=davidm@napali.hpl.hp.com \
    --cc=hch@infradead.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