Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756089AbbLAMf1 (ORCPT ); Tue, 1 Dec 2015 07:35:27 -0500 Received: from mail-wm0-f45.google.com ([74.125.82.45]:36323 "EHLO mail-wm0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752636AbbLAMf0 (ORCPT ); Tue, 1 Dec 2015 07:35:26 -0500 MIME-Version: 1.0 In-Reply-To: References: <1448622860-9689-1-git-send-email-riku.voipio@linaro.org> <20151127200710.GB17820@x> <20151130163129.9f29d40b969862d3fdbd8c20@linux-foundation.org> Date: Tue, 1 Dec 2015 14:35:24 +0200 Message-ID: Subject: Re: [PATCH v2] uselib: default depending if libc5 was used From: Riku Voipio To: Geert Uytterhoeven Cc: Andrew Morton , Josh Triplett , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1255 Lines: 29 On 1 December 2015 at 10:46, Geert Uytterhoeven wrote: > On Tue, Dec 1, 2015 at 1:31 AM, Andrew Morton wrote: >> On Fri, 27 Nov 2015 12:07:10 -0800 Josh Triplett wrote: >>> IA32_EMULATION depends on X86_64, so doesn't that reduce to: >>> def_bool ALPHA || M68K || SPARC || X86_32 || IA32_EMULATION Ok. looks cleaner to me. >> It's a bit old fashioned to add an expression like this at the >> definition site anyway. The cool new thing is to do >> >> def_bool ARCH_WANT_USELIB >> >> then go off and define ARCH_WANT_USELIB in the appropriate places in >> the per-arch Kconfig files. > > That's useful for new to-be-implemented features, but this dependency list is > (hopefully) cast in stone. No new architecture should need this. > So I see no reason to clutter up more Kconfig files. I agree. Splitting oneline patch to a patch that changes 5 files around kernel tree only risks merge conflicts in this case. Riku -- 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/