Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933007AbbENLum (ORCPT ); Thu, 14 May 2015 07:50:42 -0400 Received: from mail-wi0-f176.google.com ([209.85.212.176]:36365 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932318AbbENLuj (ORCPT ); Thu, 14 May 2015 07:50:39 -0400 MIME-Version: 1.0 From: Valentin Rothberg Date: Thu, 14 May 2015 13:50:08 +0200 Message-ID: Subject: soc/tegra: fuse: undefined option ARCH_TEGRA_210_SOC To: treding@nvidia.com Cc: Valentin Rothberg , swarren@wwwdotorg.org, gnurou@gmail.com, linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org, Paul Bolle , Andreas Ruprecht , hengelein Stefan 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: 1263 Lines: 28 Hi Thierry, your commit e3cf5bf687df ("soc/tegra: fuse: Add Tegra210 support") is in today's linux-next tree (i.e., next-20150514). The following lines in the commit reference a Kconfig option that is not defined, so that the driver and the affected #ifdef blocks cannot be compiled: drivers/soc/tegra/fuse/Makefile:10:obj-$(CONFIG_ARCH_TEGRA_210_SOC) += speedo-tegra210.o drivers/soc/tegra/fuse/fuse-tegra.c:104:#ifdef CONFIG_ARCH_TEGRA_210_SOC drivers/soc/tegra/fuse/fuse-tegra30.c:49: defined(CONFIG_ARCH_TEGRA_210_SOC) drivers/soc/tegra/fuse/fuse-tegra30.c:148:#if defined(CONFIG_ARCH_TEGRA_210_SOC) drivers/soc/tegra/fuse/fuse.h:84:#ifdef CONFIG_ARCH_TEGRA_210_SOC drivers/soc/tegra/fuse/fuse.h:104:#ifdef CONFIG_ARCH_TEGRA_210_SOC Is there a patch queued somewhere to add this option? I detected this issue with scripts/checkkconfigsymbols.py by diffing yesterday's and today's linux-next tree. You can also use the script to check specific commits for Kconfig related issues. Kind regards, Valentin -- 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/