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-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
