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
On Thu, May 14, 2015 at 01:50:08PM +0200, Valentin Rothberg wrote:
> 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?
Yes, these patches are all in the process of being merged for v4.2, so
I'd expect this particular Kconfig option to show up sometime soon now.
Thanks,
Thierry
Hi Thierry,
this is just a kind reminder that the issue (see below) is still present.
On Fri, May 15, 2015 at 10:57 AM, Thierry Reding <[email protected]> wrote:
> On Thu, May 14, 2015 at 01:50:08PM +0200, Valentin Rothberg wrote:
>> 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?
>
> Yes, these patches are all in the process of being merged for v4.2, so
> I'd expect this particular Kconfig option to show up sometime soon now.
>
> Thanks,
> Thierry
Kind regards,
Valentin