Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752146Ab0KYTKi (ORCPT ); Thu, 25 Nov 2010 14:10:38 -0500 Received: from pfepb.post.tele.dk ([195.41.46.236]:51403 "EHLO pfepb.post.tele.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751747Ab0KYTKh (ORCPT ); Thu, 25 Nov 2010 14:10:37 -0500 Date: Thu, 25 Nov 2010 20:10:35 +0100 From: Sam Ravnborg To: Michal Marek Cc: Asbjoern Sloth Toennesen , linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org, debian-kernel@lists.debian.org Subject: Re: [PATCH] kbuild, deb-pkg: support overriding userland architecture Message-ID: <20101125191035.GB20087@merkur.ravnborg.org> References: <4CD5A6C8.8030603@asbjorn.biz> <1289070320-20726-1-git-send-email-asbjorn@asbjorn.biz> <20101125143739.GC8192@sepie.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20101125143739.GC8192@sepie.suse.cz> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 971 Lines: 22 On Thu, Nov 25, 2010 at 03:37:39PM +0100, Michal Marek wrote: > On Sat, Nov 06, 2010 at 07:05:20PM +0000, Asbjoern Sloth Toennesen wrote: > > Usefull if building for sparc64 userland, because the > > sparc and sparc64 userlands use the same 64-bit kernel, > > making it impossible to always select the correct userland > > architecture for the resulting debian package. > > > > Might also be usefull, if you want a i386 userland with a amd64 kernel. > > > > Example usage: > > make DEBARCH=i386 deb-pkg > > This variable deserves a mention in Documentation/kbuild/kbuild.txt not > just in the commit log. Otherwise the patch is OK with me. kbuild related variables is usually named KBUILD_* - but not all of them. Sam -- 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/