Date: Tue, 13 May 2003 13:17:54 -0700
From: Andrew Morton <akpm@digeo.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: 2.6 must-fix list, v2
Message-Id: <20030513131754.7f96d4d0.akpm@digeo.com>
In-Reply-To: <20030513163854.A27407@infradead.org>
References: <20030512155417.67a9fdec.akpm@digeo.com>
	<20030512155511.21fb1652.akpm@digeo.com>
	<1052834227.432.30.camel@dhcp22.swansea.linux.org.uk>
	<20030513163854.A27407@infradead.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 844
Lines: 20

Christoph Hellwig <hch@infradead.org> wrote:
>
> That brings up another issue:  what ports do regularly work with 2.5
>  mainline?

I test ppc64 regularly.  In fact -mm is probably the best place to go to
get a working ppc64 tree at present.

But I do not view non-ia32 support as being a 2.6.0 requirement.  I'd be OK
with 2.6.0 working _only_ on ia32.  Other architectures will catch up when
they can.  The only core requirement is that 2.6.0 not contain gross
x86isms which make other ports impossible.

That's a rather lame position, and sure, one would wish otherwise.  Feel
free to disagree ;)
-
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/