From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757874AbcG0SMO (ORCPT ); Wed, 27 Jul 2016 14:12:14 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:34572 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753276AbcG0SMN (ORCPT ); Wed, 27 Jul 2016 14:12:13 -0400 Date: Wed, 27 Jul 2016 19:12:05 +0100 From: Mark Brown To: David Daney Cc: Jan Glauber , linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org, "Steven J. Hill" , David Daney Message-ID: <20160727181205.GT11806@sirena.org.uk> References: <20160724210452.GB6345@sirena.org.uk> <20160725155122.GA2710@hardcore> <20160725161632.GD11806@sirena.org.uk> <57963ED3.4090402@caviumnetworks.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9uazBBczf8QSjDPd" Content-Disposition: inline In-Reply-To: <57963ED3.4090402@caviumnetworks.com> X-Cookie: Are you still an ALCOHOLIC? User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 2a01:348:6:8808:fab::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 6/6] spi: octeon: Add thunderx driver X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --9uazBBczf8QSjDPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 25, 2016 at 09:31:15AM -0700, David Daney wrote: > On 07/25/2016 09:16 AM, Mark Brown wrote: > > The usual pattern would be something like (ARCH_THUNDER || COMPILE_TEST) > > && PCI && 64BIT (so that people on other platforms where the device will > > never actually appear don't get bothered by the prompt). > ARCH_THUNDER needs to die, so perhaps it should be (ARM64 || COMPILE_TEST) > && PCI && 64BIT if you really want to hide it from non-arm64 kernel configs. It does? Why? One of the functions of the vendor specific Kconfig options is to improve UX when configuring the kernel, if you're building for a particular SoC or set of SoCs then we can avoid showing you drivers that can never possibly appear in your system which makes life a bit easier. We shouldn't be using them in the code itself but they do help people in Kconfig. --9uazBBczf8QSjDPd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXmPlzAAoJECTWi3JdVIfQ0T0IAIHsB1vqdBvh3seMQu1xBclB kr+/u1vjGF9BYk5vZZ5X1m6d3dAsbdmO/8e+iXe60lMu56jbRU/++gFRV0uXc/rq NReug9xCKdu1Lh7bDiTyLWcsgeLJeYQseDgEPQL6FQUnZXh4COnEjQLJpvemGZOD c4MVDtsI0T0kgZzjuxmOig77alzm6oBwuWknbuyWO4lCgbubexVbqA6BdVJDWRZ4 G8wQ94wxY9EKLxBrMaaAT9TLogsL71y2jCLR/xCXfPczWBe7tzvn4j7/77/58+09 +KeVt+oXOBeTEvcmttfidnJK+CnO+0JpD7qgEN0qWqWK3+fauyJv2ergmi23GdU= =25zC -----END PGP SIGNATURE----- --9uazBBczf8QSjDPd--