linux-kernel - clk: tango4: undefined CONFIG_ARCH

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 20 Nov 2015 09:50:39 +0100
From:	Valentin Rothberg <valentinrothberg@...il.com>
To:	marc_gonzalez@...madesigns.com
Cc:	sboyd@...eaurora.org, linux-kernel@...r.kernel.org,
	linux-clk@...r.kernel.org, Paul Bolle <pebolle@...cali.nl>,
	Andreas Ziegler <ziegler@...fau.de>
Subject: clk: tango4: undefined CONFIG_ARCH_TANGOX

Hi Marc,

your commit ed12dfc92f01 ("clk: tango4: clkgen driver for Tango4
platforms") has shown up in today's linux-next tree (i.e.,
next-20151120) adding the following build condition to the tango4 clk
driver:

drivers/clk/Makefile:45:obj-$(CONFIG_ARCH_TANGOX) += clk-tango4.o

However, ARCH_TANGOX is nowhere defined in Kconfig so that the driver
cannot be compiled at the current state.  I checked the LKML, and found
a bunch of patches referencing ARCH_TANGOX as well, but I could not find
any patch adding this option.

Is there a patch queued somewhere that adds ARCH_TANGOX?

I detected the issue with scripts/checkkconfigsymbols.py by diffing
yesterday's and today's linux-next.

Kind regards,
 Valentin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/