Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp2195854pxv; Sat, 24 Jul 2021 08:15:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx5zi4I/eZGC2rZBkVqVxBkw/qaqIRDL5OpR2Hc2/znS32+l6kXefkkZQyQnw/xegLQVFDs X-Received: by 2002:a5d:9958:: with SMTP id v24mr7893031ios.4.1627139734756; Sat, 24 Jul 2021 08:15:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627139734; cv=none; d=google.com; s=arc-20160816; b=ij1H13Yu878g3yzGA+nu8Z931PwXmKRTlXv29dysMP8vem6qH6sFokbl5KLpI4Vfcb qzH00osQ4VBasRmQOgILQvaPsslv/xfjSmXMsmm9etVOH/ZReQC3AiLDJKHNk1E0Ukw/ /p7B71Uh9YnDC8kpI6T5wxSBTjRAE/w1dX8BPScyUzD/GEBvzszxlxFT9rQ0iq66zKL7 8+cSVMe7OCBiG6fmKOIUWMI1MMponDuC4zZE19yQlVFJtsOlWXc/OYyYeNK+iYrHSg7l WjclVypwMeMFF79RHEzD/uHgVYimQFMFDtaNUc+CicyWWAtSoATuknhJkZOaFtyx1PaE Vlwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=856ZZ8pni5gl9cA1LBBUO5cCJhsnP2Z95QrdBBWFlHs=; b=wgM7PwYzJt+i/Iv7923SlgssdZAphe0vPBFWyXIITCjFPaCoKoHf8DXOY1fuV19bn9 B0M9EdDx2r+VOFXdkoe4Yr7sgsE6psECP4zUu7ZGuO61+1m8oUDfXP2KQPDH8Z8i7Azz kBrdfH3qZFsd+29ZkaY+DWjCDqaOz1HbHmah5L/XHbWtP/iJU2+GHGYhucOPjN6Ze1HP iZ/HBmI2y08iq0mw9d+mYtH97RrPx1Z2yVmG8FMrPQcXcQtg10fhZjkhavO0Oc2NHkun 9Sd3j7EeN0CfDoEqAchQEKaV5k4p9zAql3I/Bj0A40VIjiZ/Ka2RucvGeEnfGDoFJsGR 8nfw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a24si27544114iol.81.2021.07.24.08.15.20; Sat, 24 Jul 2021 08:15:34 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229864AbhGXOdh (ORCPT + 99 others); Sat, 24 Jul 2021 10:33:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:35196 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229545AbhGXOdg (ORCPT ); Sat, 24 Jul 2021 10:33:36 -0400 Received: from jic23-huawei (cpc108967-cmbg20-2-0-cust86.5-4.cable.virginm.net [81.101.6.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id AE51960E0C; Sat, 24 Jul 2021 15:14:04 +0000 (UTC) Date: Sat, 24 Jul 2021 16:16:35 +0100 From: Jonathan Cameron To: Arnd Bergmann Cc: Andy Shevchenko , Sean Nyekjaer , Arnd Bergmann , Lars-Peter Clausen , Linus Walleij , Stephan Gerhold , Hans de Goede , Tomas Melin , Mike Looijmans , Alexandru Ardelean , linux-iio@vger.kernel.org, Linux Kernel Mailing List Subject: Re: [PATCH] iio: accel: fxls8962af: fix i2c dependency Message-ID: <20210724161635.479e5238@jic23-huawei> In-Reply-To: References: <20210721151330.2176653-1-arnd@kernel.org> X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 21 Jul 2021 20:40:30 +0200 Arnd Bergmann wrote: > On Wed, Jul 21, 2021 at 7:34 PM Andy Shevchenko > wrote: > > On Wed, Jul 21, 2021 at 7:12 PM Arnd Bergmann wrote: > > > On Wed, Jul 21, 2021 at 5:52 PM Andy Shevchenko > > > wrote: > > > > On Wed, Jul 21, 2021 at 6:13 PM Arnd Bergmann wrote: > > > > ... > > > > > > > config FXLS8962AF > > > > > tristate > > > > > + depends on I2C || !I2C # cannot be built-in for modular I2C > > > > > > > > Can you enlighten me how this will not be a no-op? > > > > > > This part does nothing, it only causes a warning when FXLS8962AF > > > gets selected =y when I2C=m. > > > > This is something new to me. But shouldn't the other chunk guarantee > > that warning won't happen? > > Correct, it works without that, but if that fails after something changes, > this version would provide better diagnostics than the FXLS8962AF > core driver causing a link failure, and I found it documents better > why the other driver needs the dependency. > > Let me know if you prefer me to resend the patch without this hunk. > > Arnd Hi Arnd, I didn't think of this particularly combination when we dealt with last build issue the workaround brought in. I've applied this to the fixes-togreg branch of iio.git as an immediately solution, but longer term we should think about just using a function pointer to allow us to move this into the i2c specific module. If we do that we can drop this complex build logic later. Thanks, Jonathan