From: jbarnes@sgi.com (Jesse Barnes)
To: Pat Gefre <pfg@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
akpm@osdl.org, davidm@napali.hpl.hp.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Updating our sn code in 2.6
Date: Fri, 19 Dec 2003 17:24:28 -0800 [thread overview]
Message-ID: <20031220012428.GA6654@sgi.com> (raw)
In-Reply-To: <200312200035.hBK0ZwWR005874@fsgi900.americas.sgi.com>
David, can you take these patches into your tree too? We'll of course
continue to clean things up, but with the application of these patches,
the 2.6 kernel becomes something really usable for people with Altix
machines.
Thanks,
Jesse
On Fri, Dec 19, 2003 at 06:35:57PM -0600, Pat Gefre wrote:
> Christoph,
>
> Some general comments/questions and then the specifics follow.
>
> First off, some of the changed/reorg'd code is foundation code for a
> new ASIC that we are working on - so it now looks a little silly and
> maybe a little like overkill, but we would like to start moving this
> code into the community base.
>
> I'm not sure where you are going with the IP27 idea. IP27 is mips so
> the code doesn't belong in the ia64 directories - we also don't support
> Bridge/Xbridge in our ia64 code which is why we'd like to get rid of it
> and if you wanted to use the code as framework for other work I would
> think you could archive a version of the tree now ? So I'm a bit
> confused - there must be something I'm missing.
>
> Also I did these patches sequentially (hence the numbering) - so in
> some cases I may have taken out code that wasn't being used at the
> time, but then added in back in when it was used.
>
> Thanks for reviewing this for me - it sounds like we are making some
> progress.
next prev parent reply other threads:[~2003-12-20 1:26 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 [this message]
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
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=20031220012428.GA6654@sgi.com \
--to=jbarnes@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