Date: Mon, 14 Aug 2006 23:17:33 -0400
From: Jeff Dike <jdike@addtoit.com>
To: Matt Mackall <mpm@selenic.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
       user-mode-linux-devel@lists.sourceforge.net,
       Joern Engel <joern@wohnheim.fh-wedel.de>
Subject: Re: [PATCH] UML - support checkstack
Message-ID: <20060815031733.GA7089@ccure.user-mode-linux.org>
References: <200608091815.k79IFQVB005310@ccure.user-mode-linux.org> <20060810020922.GO6908@waste.org> <20060810042216.GA7754@ccure.user-mode-linux.org> <20060810164548.GS6908@waste.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060810164548.GS6908@waste.org>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 870
Lines: 24

On Thu, Aug 10, 2006 at 11:45:48AM -0500, Matt Mackall wrote:
> > SUBARCH has a different meaning here.  For UML, it's the underlying,
> > host, architecture, not a variant architecture like Voyager.
> 
> Right, so it sounds like this breaks Voyager. Which I think means we
> ought to pass ARCH and SUBARCH and do the right thing inside
> checkstack.

There is no use of the symbol SUBARCH in arch/i386.  While this may be
jarring to people who know and love Voyager, it doesn't break
anything.

We could do what you suggest, but that sounds unnecessary.

I'd rather either
	leave things as they are
	rename SUBARCH

				Jeff
-
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/