Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752017AbbEFUUq (ORCPT ); Wed, 6 May 2015 16:20:46 -0400 Received: from lists.s-osg.org ([54.187.51.154]:50187 "EHLO lists.s-osg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751069AbbEFUUm (ORCPT ); Wed, 6 May 2015 16:20:42 -0400 Message-ID: <554A7798.4070502@osg.samsung.com> Date: Wed, 06 May 2015 14:20:40 -0600 From: Shuah Khan Organization: Samsung Open Source Group User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: Tyler Baker , Andy Lutomirski CC: Kevin Hilman , John Stultz , Darren Hart , David Herrmann , Michael Ellerman , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v4 4/7] selftest/x86: build both bitnesses References: <1429656693-9937-1-git-send-email-tyler.baker@linaro.org> In-Reply-To: <1429656693-9937-1-git-send-email-tyler.baker@linaro.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 991 Lines: 28 On 04/21/2015 04:51 PM, Tyler Baker wrote: > Using uname with the processor flag option in some cases can yield 'unknown' > so lets use the machine flag option as it is deterministic. Add a dependency > for all_32 when building on a x86 64 bit host so that both bitnesses are > built in this case. > > Cc: Andy Lutomirski > Acked-by: Andy Lutomirski > Signed-off-by: Tyler Baker > --- I will wait on this patch and other x85 patches in this series until x86 always build 32 breaking make kselftest target. thanks, -- Shuah -- Shuah Khan Sr. Linux Kernel Developer Open Source Innovation Group Samsung Research America (Silicon Valley) shuahkh@osg.samsung.com | (970) 217-8978 -- 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/